Update Azure pipeline queue names from vs2022 to vs2026

[Copilot]

This PR updates all Visual Studio queue name references from vs2022 to vs2026 across Azure pipeline YAML files in the repository root directory.

Changes

All queue name references have been updated to use vs2026 instead of vs2022, including:

• Queue value names: windows.vs2022.amd64.open → windows.vs2026.amd64.open
• Preview queue names: windows.vs2022preview.scout.amd64.open → windows.vs2026preview.scout.amd64.open
• Helix queue names: windows.amd64.vs2022.pre.open → windows.amd64.vs2026.pre.open
• Variable names: Vs2022PreviewQueueName → Vs2026PreviewQueueName, Vs2022RegularQueueName → Vs2026RegularQueueName
• Parameter names: vs2022PreviewPool → vs2026PreviewPool, vs2022RegularPool → vs2026RegularPool
• Pool image references and ImageOverride demands

Files Modified

• azure-pipelines-integration.yml - 5 references
• azure-pipelines-integration-corehost.yml - 5 references
• azure-pipelines-integration-lsp.yml - 5 references
• azure-pipelines-integration-scouting.yml - 5 references
• azure-pipelines-official.yml - 2 references
• azure-pipelines.yml - 16 references

Total: 42 replacements across 6 files

All YAML files remain syntactically valid and no vs2022 references remain in the repository root directory.

Original prompt

On azure-pipelines-integration.yml:75-75, This file has several references to vs2022 in queue names. Please update all the references in this file to vs2026, and also search any other .yml files in this same folder for queue names as well.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[phil-allen-msft]

Some of these names don't currently exist. (Think every changed line that lacks the word preview). I think these are reasonable predictions, but will that cause any issues in the meantime?

[dibarbet]

didn't see this before, but I am also working on #81037

It doesn't modify official build yet, only integration tests. Official build would have to be swapped to the preview scouting queue

[dibarbet]

only this one exists (applies everywhere else)

[JoeRobich]

Perennial time to ask whether we still need the corehost integration pipeline

[JoeRobich]

Seeing as it only runs up to 17.10, I would think not.

[JoeRobich]

I think these are reasonable predictions, but will that cause any issues in the meantime?

@phil-allen-msft It shouldn't cause a problem for invalid image names to be in the dropdown as long as the default value works. and no one manually queues a run against an invalid image.