_pywrap_tensorflow_internal.so library contains RUNPATH entries that look like C++ symbols
CC: @learning-to-play 
### Issue type

Bug

### TensorFlow version

2.13 - 2.16

### Python version

3.11, 3.12

### Current behavior?

The RUNPATH in the wheel shared objects is weirdly mangled:

```
$ wget https://files.pythonhosted.org/packages/0d/58/d302d19f06d028ad6c2e33c449ef9813058a16dc35c0ca9580740e0dc9ed/tensorflow-2.16.1-cp312-cp312-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
$ unzip *.whl
$ objdump -x tensorflow/python/_pywrap_tensorflow_internal.so | grep RUNPATH
  RUNPATH              $ORIGIN/../../_solib_local/_U_S_Stensorflow_Spython_C_Upywrap_Utensorflow_Uinternal.so_Ucclib___Utensorflow:$ORIGIN/_pywrap_tensorflow_internal.so.runfiles/org_tensorflow/_solib_local/_U_S_Stensorflow_Spython_C_Upywrap_Utensorflow_Uinternal.so_Ucclib___Utensorflow:$ORIGIN/../../_solib_local/_Utensorflow:$ORIGIN/_pywrap_tensorflow_internal.so.runfiles/org_tensorflow/_solib_local/_Utensorflow:$ORIGIN/:$ORIGIN/..:$ORIGIN/../../nvidia/nccl/lib:$ORIGIN/../nvidia/nccl/lib:$ORIGIN/../../tensorflow/tsl/python/lib/core
```

It's not just that one, almost every SO is affected, see:
```
find tensorflow/ -name *.so -exec objdump -x {} \; | grep RUNPATH
```

Under a custom NixOS build, this mess seems to further confuse follow-on patchelf invocations, which is requiring additional hackery to correct. Possibly related to #34991; the objdump in that ticket shows the same kind of RUNPATH.

### Standalone code to reproduce the issue

```shell
Download any wheel from PyPI, examine the `so`s contained within for their RUNPATH values.
```


### Relevant log output

_No response_