Update vcpkg-tool to 2022-06-15

[BillyONeal]

• Update vcpkg-tool to 2022-06-15. See https://github.com/microsoft/vcpkg-tool/releases/tag/2022-06-15
• Add =pass entries from Support =pass in ci.baseline.txt vcpkg-tool#579
• Cherry pick XUnit output from [ci] Publish test results #23477 which hooks up Fix xunit output errors, trim result list vcpkg-tool#585 (Thanks again @dg0yt !)
• Update release process document now that we can do the full tree rebuild to test the tool release before signing.

Thank you:

@autoantwort
@christophe-calmejane
@JackBoosY
@benmcmorran
@hmoffatt
@klalumiere
@Thomas1664
@Neumann-A
@AenBleidd

for your contributions!

Fixes #22686 .
Fixes #21800 .
Fixes #16216 .
Fixes #15836 .

Full tree rebuild testing this update is: https://dev.azure.com/vcpkg/public/_build/results?buildId=73664&view=results

[github-actions]

This is a new experimental fast check for PR issues. Please let us know if this bot is helpful!

PRs must add only one version and must not modify any published versions

When making any changes to a library, the version or port-version in vcpkg.json or CONTROL must be modified.

error: checked-in files for librttopo have changed but the version was not updated
version: 1.1.0#5
old SHA: d747c88d429ff781b11627623d0958967f912a41
new SHA: 144a5d16e71f2ceec96373e3f26b71d704bb9bec
Did you remember to update the version or port version?
Use --overwrite-version to bypass this check
***No files were updated***

[BillyONeal]

Fixes #22686 .
Fixes #21800 .
Fixes #16216 .
Fixes #15836 .

[dg0yt]

This includes the simulated build error for librttopo. Before reverting this change I would like to see a test for another new feature, by temporarily adding spatialite-tools:x64-windows = pass to the CI baseline, to be triggered by simulated error.

[BillyONeal]

This includes the simulated build error for librttopo.

Yep, already sucked it out into its own commit so that it can be force-pushed off. It works! Thank you!

Before reverting this change I would like to see a test for another new feature, by temporarily adding spatialite-tools:x64-windows = pass to the CI baseline, to be triggered by simulated error.

Stand by...

[github-actions]

This is a new experimental fast check for PR issues. Please let us know if this bot is helpful!

PRs must add only one version and must not modify any published versions

When making any changes to a library, the version or port-version in vcpkg.json or CONTROL must be modified.

error: checked-in files for librttopo have changed but the version was not updated
version: 1.1.0#5
old SHA: d747c88d429ff781b11627623d0958967f912a41
new SHA: 144a5d16e71f2ceec96373e3f26b71d704bb9bec
Did you remember to update the version or port version?
Use --overwrite-version to bypass this check
***No files were updated***

[BillyONeal]

Before reverting this change I would like to see a test for another new feature, by temporarily adding spatialite-tools:x64-windows = pass to the CI baseline, to be triggered by simulated error.

Stand by...

Does not show in the xunit output but does show on the terminal:

[dg0yt]

Does not show in the xunit output but does show on the terminal

Yes. IMO it is good enough for now. But it should be turned into an error in vcpkg tool xunit output, aligning console output with xunit. (It is possibly that this is the only error, so it should be a formal error in xunit output even if not "run".)

[BillyONeal]

@cenit I know you were looking for this =pass feature @ras0219-msft implemented.

[cenit]

@cenit I know you were looking for this =pass feature @ras0219-msft implemented.

wonderful, thanks.
I have been busy recently in many other projects, glad to see very nice improvements here in the meantime