Fixed tests from_dlpack and _from_dlpack_strided for USM-host allocations

[oleksandr-pavlyk]

Since USM-host allocation, unlike USM-device and USM-shared allocations, is not associated with any particular device, only with the host, it is unreasonable to expect that sycl::get_pointer_device(ptr, ctx) will return the same device that is stored in the sycl_queue attribute of dpctl.tensor.usm_ndarray instance.

The tests are adjusted to bypass that check for USM-host allocations.

• Have you provided a meaningful PR description?
• Have you added a test, reproducer or referred to an issue with a reproducer?
• Have you tested your changes locally for CPU and GPU devices?
• Have you made sure that new changes do not introduce compiler warnings?
• Have you checked performance impact of proposed changes?
• If this PR is a work in progress, are you opening the PR as a draft?

[coveralls]

coverage: 84.95%. remained the same when pulling f02862b on fix-dlpack-tests into 074ec3a on master.

[github-actions]

View rendered docs @ https://intelpython.github.io/dpctl/pulls/1338/index.html

[github-actions]

Array API standard conformance tests for dpctl=0.14.6dev2=py310h7bf5fec_2 ran successfully.
Passed: 913
Failed: 87
Skipped: 119

[oleksandr-pavlyk]

SYCL spec for sycl::malloc_host can be found here.

The sycl::get_pointer_device(const void *ptr, const sycl::context &syclContext) is explicitly documented so: "If ptr points within a host USM allocation for the context syclContext, returns the first device in syclContext."

[github-actions]

Deleted rendered PR docs from intelpython.github.com/dpctl, latest should be updated shortly. 🤞

[github-actions]

Array API standard conformance tests for dpctl=0.14.6dev2=py310h7bf5fec_6 ran successfully.
Passed: 913
Failed: 87
Skipped: 119