[SYCL] Enable loading cl_intel_devicelib_assert fallback spv

[jinge90]

Previously, we disabled cl_intel_devicelib_assert fallback spv in #6176 to bypass a Clang FE issue which existed in legacy compiler.
Now, the legacy compiler is out of date, we don't need this workaround any more, so enable loading cl_intel_devicelib_assert fallback spv again. This PR also updates some comments in sycl-post-link.

[AlexeySachkov]

sycl-post-link change is non-functional, LGTM

[maarquitos14]

Runtime change look good to me.

[jinge90]

Hi, @intel/llvm-gatekeepers
Could you help merge this patch? AWS CUDA test failed but it looks like to be environment issue:

" Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running hook #0: error running hook: exit status 1, stdout: , stderr: Auto-detected mode as 'legacy'
nvidia-container-cli: requirement error: unsatisfied condition: cuda>=12.1, please update your driver to a newer version, or use an earlier cuda container: unknown
Error: failed to start containers: cdf8a38d2343157c9867734eccc3c893063ba40d99fa4887681d2d1640b074bc
Error: Docker start fail with exit code 1"
Hi, @tfzhu could you confirm whether the AWS CUDA failure is caused by environment error?
Thanks very much.

[tfzhu]

Hi, @intel/llvm-gatekeepers Could you help merge this patch? AWS CUDA test failed but it looks like to be environment issue:

" Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error running hook #0: error running hook: exit status 1, stdout: , stderr: Auto-detected mode as 'legacy' nvidia-container-cli: requirement error: unsatisfied condition: cuda>=12.1, please update your driver to a newer version, or use an earlier cuda container: unknown Error: failed to start containers: cdf8a38d2343157c9867734eccc3c893063ba40d99fa4887681d2d1640b074bc Error: Docker start fail with exit code 1" Hi, @tfzhu could you confirm whether the AWS CUDA failure is caused by environment error? Thanks very much.

Need to check with @aelovikov-intel. Re-run also failed.

[aelovikov-intel]

Yes, looks like all our cuda aws testing is broken. No idea why...

[jinge90]

Hi, @intel/llvm-gatekeepers
Could you help merge this patch?
Thanks very much.