XPU: resolve the SYCL runtime by mapped path instead of a hardcoded soname
The soname is version-dependent: oneAPI 2025.x ships libsycl.so.8 while
2026.x ships libsycl.so.9, so hardcoding .so.8 silently disables host
registration after a oneAPI upgrade. Read the path of the libsycl the process
already mapped from /proc/self/maps, which both tracks the version and
disambiguates between multiple oneAPI installs on one machine.
Signed-off-by: Ma, Guokai <guokai.ma@intel.com>