Roll-forward end to end

[vitek-karas]

• SDK support - add a project property to set roll forward in the runtime config
• COM server projects should set this to LatestMinor by default - see Roll forward improvements for COM #3434
• Consider modifying the default to LatestMinor for the "component" projects as well
• Merging behavior for inner framework references - see Merging framework references with roll forward LatestMinor and LatestMajor #3550
• tracking - use LatestPatch for Microsoft.AspNetCore.App Microsoft.AspNetCore.App framework should use rollForward=LatestPatch aspnetcore#10567
• tracking - use LatestPatch for Microsoft.WindowsDesktop.App https://github.com/dotnet/core-setup/issues/6552
• Validate that the roll forward for components (and for COM servers) works as expected by default - ideally with a sample for component hosting

[vitek-karas]

SDK support implementation in PR dotnet/sdk#3296

[vitek-karas]

Implemented the merging behavior changes in PR dotnet/core-setup#6569

[vitek-karas]

Microsoft.WindowsDesktop.App switched to LatestPatch in dotnet/core-setup#6664

[vitek-karas]

SDK now supports <RollForward> msbuild property which propagates its value to the .runtimeconfig.json - dotnet/sdk#3296

[vitek-karas]

ASP.NET framework is now using LatestPatch as well - dotnet/aspnetcore#11150

[vitek-karas]

Using LatestMinor for both COM server and components has been enabled by default in https://github.com/dotnet/sdk/pull/3305/files.

[vitek-karas]

I adapted the hostfxr sample to load two separate components with different version requirements and it worked exactly as designed - no matter the other the components did load successfully.