[vcpkg-scripts] Fix rpath fixup; add test

[dg0yt]

Fix fixup for debug tools, #37736 (comment).
Fix fixup for paths with regex chars, #37984.

[JavierMatosD]

@ras0219, @data-queue, @vicroms, @BillyONeal, and I agree that fixing regex handling is absolutely good. However, expanding the definition of where debug tools should go depends on the specific use cases and we don't know of any generic use cases at this time.

That said, the DBUS situation specifically is unusual and we do believe we need to deploy the debug Daemon exe.

[dg0yt]

expanding the definition of where debug tools should go depends on the specific use cases and we don't know of any generic use cases at this time.

Sorry, but I cannot follow.
Do you want to say that tools/<port>/debug and manual-tools/<port>/debug may contain something else than debug tools?
tools/<port>/debug/bin is populated by vcpkg_configure/build/install_make, Qt5 and tcl, so there is a valid defect if the rpaths aren't fixed (EDIT:) but this is already handled by the current script.

For numbers, see #37736 (comment). Of course, this includes foo-config scripts.
For limiting the ongoing expansion, please resolve #17607.

[BillyONeal]

THANK YOU for the tests.

[dg0yt]

Nice, can we move the dbus debug tools to a proper location now?

[BillyONeal]

Nice, can we move the dbus debug tools to a proper location now?

My understanding is that the dbus situation is different because it's about how the library finds the exe but I didn't pay super close attention to the details there; I poked @data-queue and @ras0219-msft who did

[dg0yt]

it's about how the library finds the exe

I don't think I ever saw a mention of this twist. It was always about the exes finding their libs. And a little bit about cmake prefix and find stuff. Nothing specific about dbus, except the reason why the debug tools would be needed.

[ras0219-msft]

Nothing specific about dbus, except the reason why the debug tools would be needed.

The specific weird thing about dbus is that the executable is launched by the library, which means it's like a configuration-dependent "cacert.pem" thing that needs to be deployed with the final user's application. This means that users of the debug version of libdbus actually do need a debug variant of the executable dbus-daemon.

It is a non-goal (but acceptable) that the debug variant of dbus-daemon is executable from the installed directory; it eventually needs to be copied by the user into their overall product and probably rpath-adjusted to work in that environment.