Fix build break with open-source intel/llvm DPC++

[oleksandr-pavlyk]

Due to change in intel/llvm#6467 the build of SYCLInterface library is failing when using nightly sycl_bundle of intel/llvm DPC++.

This PR uses __SYCL_COMPILER_VERSION to keep both current oneAPI DPC++ and intel/llvm DPC++ working when compiling the library.

Note that sycl::device::info::max_work_item_sizes parameter is no longer in the SYCL 2020 spec rev 5, instead one should use sycl::device::info::max_work_item_sizes<1>, sycl::device::info::max_work_item_sizes<2>, sycl::device::info::max_work_item_sizes<3> and hence dpctl interfaces must be updated at some point.

• Have you provided a meaningful PR description?

[github-actions]

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

[coveralls]

Coverage decreased (-0.06%) to 81.803% when pulling 81a14dc on fix-intel-llvm-build-break into 09de29b on master.

[oleksandr-pavlyk]

I wonder if it makes sense to define dpctl.SyclDevice.max_work_item_sizes1d, dpctl.SyclDevice.max_work_item_sizes2d and dpctl.SyclDevice.max_work_item_sizes3d alongside dpctl.SyclDevice.max_work_item_sizes and deprecate the latter.

For older compilers the 1d, 2d version would simply take the first and the first two entries from the triplet returned by max_work_item_sizes.

[oleksandr-pavlyk]

@diptorupd I have implemented dpctl.SyclDevice.max_work_item_sizes1d and high dimensional analogs. The dpctl.SyclDevice.max_work_item_sizes issues Python warning.

The DPCTLDevice_GetMaxWorkItemSizes also carries deprecation warning.

Frankly, I dislike introducing these warnings. I'd say we should just remove them. It is not used in dpnp, numba_dpex so I think it should be safe to do.

[oleksandr-pavlyk]

Ok @diptorupd , I think I am going to merge this to fix build with intel/llvm DPC++ and address your feedback in a separate PR.

[github-actions]

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