[SYCL] Remove deprecated sycl device library driver options

[jinge90]

SYCL device library related driver options were marked as 'deprecated' and plans to be removed in future major release, this PR removes these driver options and clears all components dealing with these options, all related tests are updated as well.
Removing these device library related driver options is prerequisite to clear sycl device library 'online' link path in current sycl runtime and compiler which we have decided to remove to get rid of unnecessary complexity.

[aelovikov-intel]

I believe @vkurkov @stdale-intel @gmlueck and @xtian-github should decide if we can make this change now or not.

[gmlueck]

I believe @vkurkov @stdale-intel @gmlueck and @xtian-github should decide if we can make this change now or not.

We just had an email conversation about a different API breaking change, and we decided that we should wait until the oneAPI "breaking change window". I assume this falls into the same category.

[gmlueck]

Removing these device library related driver options is prerequisite to clear sycl device library 'online' link path in current sycl runtime and compiler which we have decided to remove to get rid of unnecessary complexity.

I think I may have asked this before, but I forgot. How do we plan to handle the inclusion of "libsycl-native-bfloat16.spv" vs. "libsycl-fallback-bfloat16.spv" if we remove the onlink link capability?

[jinge90]

Removing these device library related driver options is prerequisite to clear sycl device library 'online' link path in current sycl runtime and compiler which we have decided to remove to get rid of unnecessary complexity.

I think I may have asked this before, but I forgot. How do we plan to handle the inclusion of "libsycl-native-bfloat16.spv" vs. "libsycl-fallback-bfloat16.spv" if we remove the onlink link capability?

Hi, @gmlueck
We have discussion about this several months ago, the conclusion was relying on sycl dynamic libraries mechanism and embed required bf16 spvs into final executable. This was finished before oneAPI 2025.2 release and current bfloat16 functionality doesn't depend on devicelib 'online link' path.
I will send the original mail thread to you offline.
Thanks very much.

[jinge90]

I believe @vkurkov @stdale-intel @gmlueck and @xtian-github should decide if we can make this change now or not.

We just had an email conversation about a different API breaking change, and we decided that we should wait until the oneAPI "breaking change window". I assume this falls into the same category.

Yes, the original plan is to mark these devicelib related options as 'depreacted' before oneAPI 2025.2 and remove them in oneAPI 2026.0.
Thanks very much.

[srividya-sundaram]

Driver changes LGTM.

[gmlueck]

I believe @vkurkov @stdale-intel @gmlueck and @xtian-github should decide if we can make this change now or not.

We just had an email conversation about a different API breaking change, and we decided that we should wait until the oneAPI "breaking change window". I assume this falls into the same category.

Yes, the original plan is to mark these devicelib related options as 'depreacted' before oneAPI 2025.2 and remove them in oneAPI 2026.0. Thanks very much.

My understanding from @vkurkov is that we need to wait for the "breaking change window" before removing any deprecated features that are targeted for removal in 2026.0. He says that window opens on November 18, but he is working on a plan to open it on November 1.

[aelovikov-intel]

Preventing merge before ABI breaking window opens.