Update CI to .NET SDK 10.0.2xx feature band

[MartinZikmund]

Context

On 2026-04-10, .NET SDK 10.0.201 (feature band 2) became available. Our CI global.json had "rollForward": "latestMinor", which caused the agents to pick up this new SDK automatically, breaking builds:

1. Windows: SDK 10.0.201 requires MSBuild 18.0+, but our CI pool (Windows2022-20250720-1) runs VS 2022 with MSBuild 17.x
2. Linux/Android: The matching runtime 10.0.5 needs Microsoft.NETCore.App.Runtime.Mono.linux-x64 which isn't on NuGet.org

As a hotfix, we changed rollForward to "latestPatch" to pin CI to SDK 10.0.1xx.

TODO

• Update CI agent pools to include VS with MSBuild 18.0+ support (or switch to windows-latest / a newer pool image)
• Update build/ci/net10/_global.json SDK version to 10.0.201
• Verify all builds (Windows, Android Skia, iOS, WASM) pass with the new SDK
• Decide on the appropriate rollForward policy going forward (latestPatch vs latestFeature)

Files

• build/ci/net10/_global.json
• build/ci/templates/dotnet-install.yml
• .vsts-ci.yml (CI pool variables)

[Youssef1313]

Decide on the appropriate rollForward policy going forward (latestPatch vs latestFeature)

It's definitely your call, just my two cents.

Using latestPatch was my original recommendation and is what I personally think is appropriate. I originally introduced it in #10122 but was later changed in #12198. Note that both PRs I mentioned (IIRC) were before introducing CI-specific global.json (which I think you should try to get rid of). The global.json for local and CI builds should be the same IMO, and should use latestPatch. This adds a bit of hassle in that developers in the team or external contributors need to keep their local machines with the correct SDK version installed, but I personally don't think it's a big problem.