[Driver][SYCL] Use LLVM-IR based device libraries for device linking

[mdtoguchi]

This is try #2 for this - original change was suspected of breaking the device library builds.

This change represents 2 changes.

1. Update the build to create LLVM-IR based device libraries.

This is done by using the existing -fsycl-device-only functionality to create the device libraries that are used during device link.

2. Update the compiler driver to use the LLVM-IR based device libraries.

When performing the device linking instead of performing a full unbundle of the device libraries and using the device binary that was extracted.

This streamlines the device linking behaviors, completely removing the cumbersome unbundling step from the process, freeing up a number of exteral tool calls.

[asudarsa]

The AMD/HIp failure is unrelated and has been reported here (Thanks Yury Plyakhin)
#13612

Thanks

[asudarsa]

LGTM. Thanks

[sarnex]

My bad on this one, I've never seen the docker image get destroyed before!

[mdtoguchi]

@intel/dpcpp-clang-driver-reviewers, @intel/llvm-reviewers-runtime, please review. The original change was reverted due to some build problems that started occurring about the same time as the original PR being merged. Turns out that these changes were not the offending issue and can be re-applied.

[hchilama]

Driver Changes LGTM

[asudarsa]

@intel/llvm-gatekeepers , please merge. AMD/HIP failure is not related. I see other PRs have it as well:

Thanks

[steffenlarsen]

LGTM!

[hdelan]

Would it make sense to bundle all of these bc objs into a single bc library, like the way libclc is built? Then you would have a single devicelib library for each triple (or maybe a single bc lib for each triple-os pair).

Or is there some reason for keeping the devicelib objs split per TU?