Track runtimes of Windows pipelines with 5 releases

This week I have been performing dry runs for the April 2024 release cycle.
Since we have five releases in parallel, some platforms will take longer than usual to work through the list they are all initiated. This is the first time we'll have done five, with 4 being initiated previously (8, 11, 17, 21 - 22 is the new one with 21 in LTS alongside all of the others)

I have already removed win32 from the default triggers on 8, 11 and 17 (We do not build win32 for 21+) which should reduce contention (We will start a separate pipeline for those) and we are also in the process of switching off some of our windows machines and replacing them with more up to date versions as per #3238) Most of this issue will involve the gathering of data to show how things are going and determine any improvements we can make going forward.

The issue names Windows pipelines for releases 8, 11, 17, 21, and 22, plus the win32 trigger changes and related issue #3238, but no files or tests. Start by locating those pipelines and gathering their runtime data; done means reporting how the five-release setup performs and identifying improvements for future release cycles.

Written by the indexing model from the issue text.