Triage sycl-ls failures after 6ac6312

[jsji]

Describe the bug

After 6ac6312 ,
we are seeing runtime failures due to this bug in syl-ls in post-commit.
So we reverted it in pulldown PR first for now.

We should triage to see whether this is the same root cause as llvm/llvm-project#24952

https://github.com/intel/llvm/actions/runs/14204467394/job/39799261846?pr=17710

Run SYCL_UR_TRACE=1 sycl-ls
Stack dump without symbol names (ensure you have llvm-symbolizer in your
PATH or set the environment var `LLVM_SYMBOLIZER_PATH` to point to it):
0  libsycl.so.8         0x00007f531e3576e2
1  libsycl.so.8         0x00007f531e354b6e
2  libc.so.6            0x00007f531db84330
3  libur_loader.so.0    0x00007f531ccd0cd6
4  libur_loader.so.0    0x00007f531ce3e71c
5  libur_loader.so.0    0x00007f531cc780c5
6  libur_loader.so.0    0x00007f531cc7a37c
7  libur_loader.so.0    0x00007f531cc6bb5f urLoaderTearDown + 31
8  libsycl.so.8         0x00007f531e206872
9  libsycl.so.8         0x00007f531e209597
10 ld-linux-x86-64.so.2 0x00007f531e55d0f2
11 ld-linux-x86-64.so.2 0x00007f531e561578
12 libc.so.6            0x00007f531db86a76
13 libc.so.6            0x00007f531db86bbe
14 libc.so.6            0x00007f531db691d1
15 libc.so.6            0x00007f531db6928b __libc_start_main + 139
16 sycl-ls              0x000056195f04c9d5
Segmentation fault (core dumped)

### To reproduce

_No response_

### Environment

_No response_

### Additional context

_No response_