[WIP] feat: Integrate wheel repairer

[LecrisUT]

The goal of this is:

• Get the linked libraries from the configure step
• Check if the paths start with the current build environment's sysconfig.get_path("platlib")
• If so patch the RPATH to be relative paths. (Remove any hard-coded RPATHS, due to CMAKE_INSTALL_RPATH_USE_LINK_PATH)
• Patch the RPATHs of the current wheel files
• For windows systems, add dlls to Scripts path
• Do some other magic that delvewheel does

Still working on the logic for this, but there are a few questions that could be explored in the meantime.

To discuss:

• Should this be separated as a standalone plugin and instead expose an entry-point scikit-build.repair-wheel?
• Initially I was considering using auditwheel/delocate/delvewheel directly, but these do not handle differently the packages in site-package vs external
• Do we extend the interface to pick up system packages as well? I was thinking that the repairwheel trio can do all the hard work generally, but maybe the user needs more nuanced configuration, e.g. with Qt/PySide the requirement is to bundle the Qt framework uniquely, compared to dlevewheel which creates separate dlls for each wheel.
• Naive binary wrappers (e.g. tests/packages/repair_wheel/python/repair_wheel/__main__.py) can still fail because the PATH is not propagated
• Windows patching might be tricky for the compiled python module