Handling executables (scripts from the Python POV) that link to distribution libraries

I don't think auditwheel fixes the binary dependencies for wheel scripts, we should confirm that. If it does not, we should put them in platlib and add a wrapper that just calls them in the scripts directory.

The issue here is that we do not know the final location of the `.libs` folder so we cannot set the path to point there. By placing them in platlib, we can set the rpath to `$ORIGIN/../.libs`.

Start by confirming whether auditwheel fixes binary dependencies for wheel scripts and determine how wheel scripts, platlib, the scripts directory, and the .libs folder are handled. Then evaluate the proposed platlib placement and $ORIGIN/../.libs path. Done means executables that link to distribution libraries work from installed wheels with a wrapper in the scripts directory.

Written by the indexing model from the issue text.