Run Windows CI across all supported Python versions

[ichard26]

Let's see how slow or not slow this is...

This still needs updates to the development documentation.

[ichard26]

They're on par with the rest of the CI jobs. This should be okay to deploy. PTAL.

[sbidoul]

My only reservation would be that the probability of failure in those jobs (that would not also be revealed by the linux jobs) is so low that it may not be worth the additional heating of the planet.

[notatallshaw]

My only reservation would be that the probability of failure in those jobs (that would not also be revealed by the linux jobs) is so low that it may not be worth the additional heating of the planet.

Following this logic, shouldn't everything that isn't latest/oldest be turned off other than macos-latest? Which seems to be the fastest of all the CI jobs.

Then all the other Python versions can be run on a schedule, like in #13014.

My only strong opinion here is that all versions of Python for all supported OSes should be tested before a release. OS-Python version specific issues do come up with pip.

[notatallshaw]

I'm going to (cheekly) put this on to the 25.0 milestone, so this approach can be accepted or rejected by then, discussion was here: #13011