Debug Windows CI failures

[embg]

This draft PR will allow me to ssh into a windows CI machine so I can debug the recent windows CI failures. For some reason the tests are passing on my zstd fork, so I have to create a PR on the main repo.

[embg]

I was not able to ssh into a windows CI machine, but comparing logs here vs my own fork did reveal the problem. For some reason, CI on my fork resolved windows-latest to windows-2019 while CI on the main repo resolved it to windows-2022. This explains why I could not reproduce the failures on my own fork. I replaced all instances of windows-latest with windows-2019 in our workflows and it fixed the broken tests.

For discussion: should we add tests for Visual Studio 2022? Currently we have tests covering 2019 and 2015. We could remove the 2015 tests and replace them with tests for 2022 (or keep 2015 and just add 2022). I can put up a separate PR with that change (so we can merge this ASAP to unbreak CI).

Edit: created an issue for VS 2022 discussion #3064

[paolobarbolini]

For discussion: should we add tests for Visual Studio 2022? Currently we have tests covering 2019 and 2015. We could remove the 2015 tests and replace them with tests for 2022 (or keep 2015 and just add 2022). I can put up a separate PR with that change (so we can merge this ASAP to unbreak CI).

I think this would make it easier to get seanmonstar/reqwest#1464 through