Return to latest windows on CI Runners #1038

Recently the windows runners changed to Windows Server 2025, and it is causing stalls/hangs on conformance testing.

This change happened this summer and this is reflected in sudden and repeated test failures happening around the release of 1.15.0:

Obviously the release nor the CI version bumps that came after caused this breakage, the most obvious culprit is the change of Github's CI runners under the cover (note that tests also pass for all other platforms).

While the conformance tests shouldn't hang on windows, they currently do, and it would be great if someone with a windows machine/that spends lots of time in windows could look at this and attempt to reproduce or narrow down the test that is causing the hang.

The conformance test suite is generated, so testing is a bit more involved/annoying, but it's possible to debug this even from CI itself on a fork and get a reasonably fast dev loop going.

NOTE: Somewhat sneakily, the revert to windows-2022 runners happened in a dependabot PR. To get started trying to track down the issue with the more recent windows runner, the first step is to switch back to windows-latest (or more accurately windows-2025).