require exact version match for CMake and PowerShell

[Be-ing]

CMake is included in the ABI info, so an exact version match is required
for binary caching to work for sharing a cache between machines with
different environments. Refer to the comment in the code for more
details.

[Be-ing]

Is this an acceptable fix for ABI info mismatches between servers and developers' machines? An alternative would be removing the CMake and PowerShell versions from the ABI info, but I presume you had some reason to add them in the first place.

[Neumann-A]

Hmm I wish there were a switch to disable CMake and PowerShell Abi tracking.

[Be-ing]

I think adding yet another option would be a bad way to solve this. It is already necessary to disable compiler tracking to make binary caching somewhat usable. Users shouldn't need to figure out they need to switch two options away from the default to make binary caching usable. If it is permissible to not track the CMake and PowerShell versions then I think it simply shouldn't be done without having an option.

[Osyotr]

I can understand why CMake version is tracked, but why is PowerShell? I very much like the idea of having a switch to disable ABI tracking for these tools.

[Be-ing]

I think adding another option would be the worst way this could be solved.

I can understand why CMake version is tracked

Can you explain? I don't understand what that has to do with ABI.

[Be-ing]

Could a maintainer please take a look at this? This is holding back Mixxx from switching from vcpkg archive to manifest mode, which we are trying to use so we can run Qt5 and Qt6 builds on the same branch while we transition to Qt6.

[Osyotr]

Can you explain? I don't understand what that has to do with ABI.

You are right, it does not. My guess is that it has something to do with how library is consumed (config file generated for specific version etc.)

[Be-ing]

Pinging on this again. We have had several new contributors trying to build Mixxx on ARM macOS but not succeeding with the legacy vcpkg archive setup. We have had success building with vcpkg manifest mode on ARM macOS, but we cannot merge support for manifest mode until this issue with binary caching is resolved. We can't risk turning away new contributors because they have to spend hours building a huge dependency graph because vcpkg misses the cache.

[Be-ing]

Superseded by #234