[v20.x] doc: support toolchain with Visual Studio 2019 & 2022 only

[MikeMcC399]

Refs: #60869
Refs: #61449

Situation

The Supported toolchains section for v20.x lists Visual Studio >= 2019 with the Windows 10 SDK on a 64-bit host.

By implication, this includes also the latest release of Microsoft Visual Studio which is Visual Studio 2026.

.\vcbuild fails to run in the v20.x branch on Windows 11 25H2 in a PowerShell terminal with the Windows Prerequisites installed, and only using Visual Studio Build Tools 2026.

Support for Visual Studio Build Tools 2026 requires a minimum of gyp-next@0.21.0.

The Node.js v20.x branch includes gyp-next@0.16.2 in v20.x/tools/gyp and so lacks support for Visual Studio 2026.

Failure log

 .\vcbuild
Looking for Python
Python found in C:\Users\mikem\AppData\Local\Microsoft\WindowsApps\\python.exe
Python 3.14.2
Looking for NASM
Looking for Visual Studio 2022
Looking for Visual Studio 2019
Failed to find a suitable Visual Studio installation.
Try to run in a "Developer Command Prompt" or consult
https://github.com/nodejs/node/blob/HEAD/BUILDING.md#windows

Change

In BUILDING.md

• restrict to Visual Studio 2019 & 2022 for toolchain (see Build fails with Visual Studio 2026 #60869 (comment) for reasoning)
• tie reference to "Visual Studio 17.6.0 or newer" explicitly to Visual Studio 2022

[nodejs-github-bot]

Review requested:

• @nodejs/build
• @nodejs/tsc

[MikeMcC399]

@StefanStojanovic

Thanks for your support and follow-up! I think commit-queueAdd this label to land a pull request using GitHub Actions. only works for PRs targeting the main branch (see Commit Queue), so I would expect that this PR would need to be manually picked up by the Releasers / Backporters team.

[MikeMcC399]

Modified commit message to use imperative verb and rebased

[marco-ippolito]

Landed in 0f4ffc0