Manually backflow sources from dotnet/dotnet

[premun]

Backflow of build 282002

Unblocks problems that happened due to double-backflowing to main from 10.0.1xx and main VMR branches.

[github-actions]

This PR is targeting main, which is now for .NET 11-facing work. If you intended to target .NET 10, either retarget this PR to release/10.0.1xx or make sure you backport the change to release/10.0.1xx after merging. See #50394 for more details.

[Copilot]

Pull Request Overview

This PR performs a manual backflow of sources from the dotnet/dotnet VMR (Virtual Monorepo) repository to address issues caused by double-backflowing between the 10.0.1xx and main branches.

Key changes:

• Updates tool pack selection logic to better handle portable vs non-portable runtime identifiers
• Replaces Razor JSON serialization with a new custom implementation
• Updates various package versions and build configuration files

Reviewed Changes

Copilot reviewed 55 out of 57 changed files in this pull request and generated 5 comments.

Show a summary per file

File	Description
src/Tasks/Microsoft.NET.Build.Tasks/ProcessFrameworkReferences.cs	Enhanced tool pack selection logic for portable RIDs
src/RazorSdk/Tool/	Replaced old JSON converters with new custom implementation
src/Layout/	Updated template bundling and build configurations
eng/	Updated package versions and build tooling references
global.json	Updated Arcade SDK versions

[premun]

@marcpopMSFT @SimonZhao888 I am trying to fix the backflow of VMR into SDK's main (there was a misconfiguration of subscriptions and build from 10.0 and main have backflown into main here).

I see the changes done here also made in the VMR but let me know if this is not reverting something that the interbranch merging did before.

[SimonZhao888]

I see the changes done here also made in the VMR but let me know if this is not reverting something that the interbranch merging did before.

I didn't find any reverting codes in this PR, except Version.Details.props and Version.Details.xml, it seems that the referenced package version has been downgraded.

[premun]

Thanks for checking. I think the V.D.xml is clashing with the latest merge of 10.0 into main.

However, V.D.xml and will keep conflicting if we keep backflowing to both main and 10.0 as each branch will receive some version of the VMR packages (one day one might be higher while the other it can be the opposite just solely depending on the fact of which commit will build first in the VMR).

[premun]

@SimonZhao888 I found out the code in main relies on some razor packages which are only changed in main. So we won't be able to merge any changes of Version.Details.xml from 10.0 to main (so the whole file should be omitted during the merges, not just the <Source> tag)

[premun]

Suffers from similar problems as #50648

[SimonZhao888]

@SimonZhao888 I found out the code in main relies on some razor packages which are only changed in main. So we won't be able to merge any changes of Version.Details.xml from 10.0 to main (so the whole file should be omitted during the merges, not just the <Source> tag)

Got it!

[mmitche]

@marcpopMSFT This backflow should unblock things.

[premun]

Closing in favour of dotnet/dotnet#2352