Use rolling Windows queue for latest Windows tests

[agocke]

Switch the latest public Windows x64 Helix alias from the version-pinned Windows 11 client queue to the rolling runtime queue. Update CoreCLR queue selection to consume the central latest aliases for Windows x64, CET, and ARM64, and route the primary generic libraries Windows x64 tests through the latest alias.

Alias	Previous queue	New queue
helix_windows_x64_latest	Windows.11.Amd64.Client.Open	Windows.Amd64.Open.rt

Explicitly versioned Windows queues, including Windows 10, Windows Server, CET, ARM64, Nano, and the oldest aliases, remain unchanged.

Validation: git diff --check and queue-mapping assertions. The rolling queue was previously exercised by #132328.

Note

This pull request description was generated by GitHub Copilot.

[azure-pipelines]

Azure Pipelines:
Successfully started running 5 pipeline(s).
11 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

[dotnet-policy-service]

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

[Copilot]

Copilot review overview

Review tier: Lite
Findings: 1 · 1

New issues introduced by this change (2)

Severity	Finding
	eng/​pipelines/​helix-platforms.yml — The comment header for the Windows x64 “Latest” section is now ambiguous: it implies the whole…
	eng/​pipelines/​coreclr/​templates/​helix-queues-setup.yml — This change switches the internal windows_x64 CoreCLR Helix queue from a Windows 10 queue…

What changed in this PR

This PR updates Helix queue aliasing for Windows to move the public “latest” Windows x64 queue from a version-pinned Windows 11 client queue to the rolling runtime Windows queue, and updates CoreCLR’s queue selection template to consume the centralized Windows queue variables (x64, CET, and ARM64).

Changes:

• Update helix_windows_x64_latest to use Windows.Amd64.Open.rt (rolling runtime queue).
• Update CoreCLR Helix queue selection to use $(helix_windows_x64_latest), $(helix_windows_x64_latest_cet), and $(helix_windows_arm64_latest*) variables instead of hard-coded queue names.

File	Description
eng/​pipelines/​helix-platforms.yml	Switch the public Windows x64 “latest” queue alias to the rolling runtime queue and adjust related commentary.
eng/​pipelines/​coreclr/​templates/​helix-queues-setup.yml	Use centralized helix-platform variables for Windows x64/CET and Windows ARM64 queue selection.

[Copilot]

Copilot review overview

Review tier: Lite
Findings: 2 · 1

New issues introduced by this change (1)

Severity	Finding
	eng/​pipelines/​libraries/​helix-queues-setup.yml — This change replaces the explicit primary Server2025 queue with $(helix_windows_x64_latest). That…

Pre-existing issues (2)

Severity	Finding
	eng/​pipelines/​coreclr/​templates/​helix-queues-setup.yml — This change switches the internal windows_x64 CoreCLR Helix queue from a Windows 10 queue… View comment
	eng/​pipelines/​helix-platforms.yml — The comment header for the Windows x64 “Latest” section is now ambiguous: it implies the whole… View comment

Suppressed comments (1)

eng/pipelines/coreclr/templates/helix-queues-setup.yml:154

• CoreCLR internal Windows x64 queue selection changes from the explicit Windows.10.Amd64 to $(helix_windows_x64_latest_internal) (currently Windows.11.Amd64). If the goal here is only to update public/"latest" routing, consider keeping the internal queue pinned to Windows 10 (e.g., $(helix_windows_x64_oldest_internal)) or update the PR description to call out the internal OS bump explicitly.

 - ${{ if eq(variables['System.TeamProject'], 'internal') }}:
- $(helix_windows_x64_latest_internal)

[agocke]

/ba-g failures are #132830

[jkotas]

Windows.Amd64.Open.rt does not have machines with AVX512. It runs on AMD EPYC (Dav4).

Do we have sufficient coverage for AVX512 codegen and AVX512-specific optimizations in libraries after this change? cc @dotnet/jit-contrib @tannergooding