Remove local (in-group) atomic usage from __parallel_find_or (V1)

[SergeyKopienko]

In this PR we remove local (in-group) atomic usage from __parallel_find_or implementation:

• __found_local now is local variable (for each item);
• barriers doesn't required anymore;
• we updates the state of __found_local within one group through __dpl_sycl::__reduce_over_group operation :

                    __found_local = __dpl_sycl::__reduce_over_group(__item_id.get_group(), __found_local,
                                                                    typename _BrickTag::_LocalResultsReduceOp{});

where _LocalResultsReduceOp is :

• __dpl_sycl::__minimum (for the __parallel_find_forward_tag);
• __dpl_sycl::__maximum (for the __parallel_find_backward_tag);
• __dpl_sycl::__bit_or (for the __parallel_or_tag).

The new operation __dpl_sycl::__bit_or has been defined in the file sycl_defs.h :

#if _ONEDPL_SYCL2020_FUNCTIONAL_OBJECTS_PRESENT
// ...
template <typename _T = void>
using __bit_or = sycl::bit_or<_T>;
#else  // _ONEDPL_SYCL2020_FUNCTIONAL_OBJECTS_PRESENT
// ...
template <typename _T = void>
using __bit_or = sycl::ONEAPI::bit_or<_T>;
#endif // _ONEDPL_SYCL2020_FUNCTIONAL_OBJECTS_PRESENT

[SergeyKopienko]

Described at https://github.com/intel/llvm/blob/sycl/sycl/doc/extensions/removed/sycl_ext_oneapi_group_algorithms.asciidoc

[SergeyKopienko]

Described at https://registry.khronos.org/SYCL/specs/sycl-2020/html/sycl-2020.html#table.identities

[SergeyKopienko]

Test evidence for complier icx 2021.1.2 (whene group operations isn't present) ): https://godbolt.org/z/PcnYT4vqe

[SergeyKopienko]

@danhoeflinger, @julianmi is something that mandatory required to change in this PR?

[julianmi]

LGTM. Please wait for @danhoeflinger and green CI.

[danhoeflinger]

LGTM, with the comment explaining the restriction of workgroup size, it is OK.
I believe we can just make that restriction for all targets, but it should be examined, and we can do that in a separate PR.