[vcpkg] Revise appdeploy and copy_tool_dependencies

[dg0yt]

• What does your PR fix?

  • [appdeploy] Fixes deployment for mingw on linux by
    • making path construction portable,
    • catching failing fixing mutex creation.
  • [copy_tool_dependencies] Enables deployment for debug config.
  • [copy_tool_dependencies] Fixes overwriting of log files within a single port build.
  • [copy_tool_dependencies] Enables actual logging at least when DEBUG_PORT is set (cf. debug_message in ports.cmake).

• Which triplets are supported/not supported? Have you updated the CI baseline?

  all, no

• Does your PR follow the maintainer guide?

  yes

• If you have added/updated a port: Have you run ./vcpkg x-add-version --all and committed the result?

  --

• For discussion

  • Logging (-verbose) might always be enabled. It doesn't clutter output.
  • If there is a better idea how to deal with the mutex creation issue...
  • To correctly handle some port being set to a single config (via triplet file), it would be necessary to also search the alternative bin directory.
  • It is not efficient to call appdeploy.ps1 twice. It should better take a list of directories as search path instead of a single directory.
    And it should also take a list of executables (or just a single directory).

[dg0yt]

The original mutex error on linux:

New-Object: /home/kpa/Projekte/vcpkg/vcpkg/scripts/buildsystems/msbuild/applocal.ps1:26:16
Line |
  26 |          return New-Object System.Threading.Mutex($false, $mtxName)
     |                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
     | Exception calling ".ctor" with "2" argument(s): "The filename, directory name, or volume label syntax is incorrect. :
     | 'VcpkgAppLocalDeployBinary-/67pRTB1Ups2rRbHaFf9MmG5+3JTeHXhgLDIy6xHo3Wsrcl2RLAMD0XgKTwuKrwUcHqwWB5xF+iuO1frfY0xZQ=='"

[dg0yt]

The original mutex error on linux

... is caused by the / in the mutex name.

[JackBoosY]

@BillyONeal Can you please review this PR?
Thanks.

[dg0yt]

Minor output change here.

[ras0219-msft]

It is not efficient to call appdeploy.ps1 twice. It should better take a list of directories as search path instead of a single directory.
And it should also take a list of executables (or just a single directory).

110% agreed. Additionally, using powershell for this has shown to be no longer sufficient. Both @BillyONeal and I have medium term desires to nuke this in favor of a small portable C++ utility (maybe separate, maybe built-in to vcpkg.exe), however the need for extensibility for plugin producers (Qt, magnum, etc) has made that non-trivial. I hope to eventually find a simple text/json format that can capture all needed information for those cases in a declarative way (and we can add a small amount of hardcoded logic for backwards compatibility to older port versions).

[dg0yt]

It is not efficient to call appdeploy.ps1 twice. It should better take a list of directories as search path instead of a single directory.
And it should also take a list of executables (or just a single directory).

110% agreed.

I just can't put too much in a single PR.

[ras0219-msft]

Thanks!