win-64 builds temporarily broken while Azure transitions to Visual Studio 17.11

[jdblischak]

The Azure Windows Server 2022 image is transitioning from Visual Studio 17.10 to 17.11. They keep switching back and forth, making it difficult to update the conda-forge infrastructure against this moving target. Hopefully it will stabilize on 17.11 soon.

Once the new image is deployed, we need to:

• restart the failed win-64 CI on the latest merge commit cf2ac8c for the aws_crt_cpp 0.28.0 migration (Rebuild for aws_crt_cpp 0.28.0 #336)
• restart the failed win-64 CI for the aws_crt_cpp 0.28.1 migration PRs (Rebuild for aws_crt_cpp 0.28.1 #338, Rebuild for aws_crt_cpp 0.28.1 #339)

xref: TileDB-Inc/conda-forge-nightly-controller#133

[jdblischak]

It looks like they once again transitioned to 17.11. I restarted the previously failed win-64 job https://dev.azure.com/conda-forge/feedstock-builds/_build/results?buildId=1011731&view=logs&j=8af117b0-dfa5-5d1c-b02e-a448dd16efdb

[jdblischak]

Nope. That failed. They must be slowly rolling out the new image, because now my jobs only get the old image.

[jdblischak]

I managed to apply both migration PRs. New binaries have been uploaded that were built against aws_crt_cpp 0.28.1

• 2.25 on main (3626b44)
• 2.24 on 2.24.x (c91a9c2)

Not worth worrying about the previously failed win-64 build. It was to build against aws_crt_cpp 0.28.0, which has clearly already been superseded