[SYCL][E2E] Use target- requirements in tests that fail to build for all triples

[ayylol]

These tests fail building for all triples, so this pr adds target- requirements to avoid compiling for those triples while in build-only. Previously when in full testing mode these tests were either marked as unsupported for the backend corresponding to a given triple, or required a feature that implicitly made some triples unsupported (i.e., accelerator, or sg-8).

[ayylol]

@intel/dpcpp-spirv-reviewers Friendly ping

[AlexeySachkov]

These tests fail building for all triples, so this pr adds target- requirements to avoid compiling for those triples while in build-only.

Strictly speaking, that indicates issues in implementation and/or language design of corresponding features. They should either work everywhere, or be guarded by corresponding aspects and therefore be handled by optional kernel features mechanism.

There is no a generic solution for that and I'm not going to object, but list of updated files is a very good list of features which require a more detailed look at them - they all highlight places where "single source runs everywhere" doesn't work at the level "we can't compile it".

[ayylol]

Added two more tests to this pr (ClusterLaunch/enqueueLaunchCustom_check_event_deps.cpp and SubGroup/attributes.cpp). Confirmed that they needed the extra markup here https://github.com/intel/llvm/actions/runs/13203760519/job/36861895735

[ayylol]

@intel/llvm-gatekeepers this is ready to merge. AMD test failure is #16933. Opened new issue for NVIDIA test failure #16951 (Again, this PR is individual test changes and that test is not touched)