Add check to ensure loaded port matches the declared version

[ras0219-msft]

Fixes microsoft/vcpkg#20503.

The fundamental issue in the thread was that the user's versions database did not match the actual retrieved files. This PR addresses the problem by adding an integrity check to ensure that files retrieved from a registry match the version declared in that registry's database files.

Before:

❯ vcpkg install --triplet x64-windows
Error: Cycle detected during arrow:x64-windows:
bloom-filter:x64-windows

After:

❯ vcpkg install --triplet x64-windows
Error: Failed to load port from D:\src\cycle_detected\./vcpkg_registry\ports/arrow: version specs did not match: 'arrow@6.0.0.20210925#4' != 'arrow@6.0.0.20210925'
Error: Failed to load port from D:\src\cycle_detected\./vcpkg_registry\ports/arrow: version specs did not match: 'arrow@6.0.0.20210925#4' != 'arrow@6.0.0.20210925'

The error is emitted twice because it is checked every time the algorithm attempts to load the file. The errors are accumulated and presented at once, which currently results in duplication.

Potential improvements to this PR:

• Add an e2e test
• Don't print duplicate errors
• Localize

[BillyONeal]

I think investigating what happened was high priority but this has been in the product for more than a year, so I don't think avoiding adding the e2e test to get it a day or 2 earlier is reasonable.

As for not printing duplicates, isn't that a call to Util::sort_unique_erase away?

[BillyONeal]

As for not printing duplicates, isn't that a call to Util::sort_unique_erase away?

It was, and I pushed that.

[BillyONeal]

Localizing the error message changed the content which made the e2e test fail, I pushed a fix.