[SYCL] Make joint_reduce work with sub_group (intel#8786)

Note: the unqualified name lookup of joint_reduce in the overload of
joint_reduce without an init param was not finding the overload of
joint_reduce with an init param (because that declaration was located
after it), so it searched for joint_reduce via ADL. With sycl::group,
ADL can find both overloads of joint_reduce, but with sycl::sub_group =
sycl::ext::oneapi::sub_group, ADL finds no joint_reduce in
sycl::ext::oneapi.

Fixes intel#8348

---------

Signed-off-by: Cai, Justin <[email protected]>

Merged to sycl-web with no conflict or build issue

Ready to continue

Merged to sycl-web with no conflict or build issue

Build passed

[SYCL] Make joint_reduce work with sub_group (intel#8786)

Note: the unqualified name lookup of joint_reduce in the overload of
joint_reduce without an init param was not finding the overload of
joint_reduce with an init param (because that declaration was located
after it), so it searched for joint_reduce via ADL. With sycl::group,
ADL can find both overloads of joint_reduce, but with sycl::sub_group =
sycl::ext::oneapi::sub_group, ADL finds no joint_reduce in
sycl::ext::oneapi.

Fixes intel#8348

---------

Signed-off-by: Cai, Justin <[email protected]>

[SYCL] Do not track allocation if we don't own the handle (intel#8792)

If we don't own level zero handle of the pi_mem then we can't control
deallocation of that memory so there is no point of keeping track of the
memory allocation for deferred memory release. More over currently level
zero context is leaked because we increase its ref count at the point
where we start tracking memory but don't decrement that ref count in
USMFreeHelper. This PR fixes that problem.

[SYCL] Kernel property to control Cache/SLM size on GPU (intel#8597)

When L1 cache & SLM share same physical memory module, developers may
want more L1 or SLM based on their application. So, the purpose of the
introduced kernel property is to give developers flexibility to tune the
division.

E2E test: intel/llvm-test-suite#1687

[SYCL][InvokeSIMD] Add test for invoke_simd return type error (intel#…

…8772)

Based on intel/llvm-test-suite#1679

Signed-off-by: Sarnie, Nick <[email protected]>

[SYCL] Diagnose local accessor use in single_task or parallel_for(ran…

…ge) (intel#8581)

* According to [local
accessors](https://registry.khronos.org/SYCL/specs/sycl-2020/html/sycl-2020.html#sec:accessor.local)
of the SYCL specification, a local accessor must not be used in a SYCL
kernel function that is invoked via single_task or via the simple form
of parallel_for that takes a range parameter.
* Add test.

---------

Co-authored-by: Alexey Bader <[email protected]>