[clr-ios] Support targeting Apple mobile platforms with CoreCLR

[kotlarmilos]

Description

This PR adds Apple mobile rids to the NetCoreRuntimePackRids to support targeting CoreCLR.

[akoeplinger]

LGTM apart from my comments

[Copilot]

Pull Request Overview

This PR adds support for targeting Apple mobile platforms (iOS, tvOS, and Mac Catalyst) with CoreCLR by introducing new runtime identifiers (RIDs) for .NET 11.0.

Key Changes:

• Introduces Net110RuntimePackRids containing Apple mobile platform RIDs (ios-arm64, iossimulator-arm64/x64, tvos-arm64, tvossimulator-arm64/x64, maccatalyst-arm64/x64)
• Updates NetCoreRuntimePackRids to reference the new .NET 11.0 RID collection
• Maintains backward compatibility by keeping .NET 10.0 RIDs for KnownFrameworkReference targeting pack references

[MichaelSimons]

This change regressed source build when it flowed into the VMR. Can someone explain this particular change? This causes this special SB logic to be skipped.

[rolfbjarne]

This change regressed source build when it flowed into the VMR. Can someone explain this particular change? This causes this special SB logic to be skipped.

That's how it's done in the .NET 9 case:

sdk/src/Layout/redist/targets/GenerateBundledVersions.targets

Line 824 in 1b7a79f

RuntimePackRuntimeIdentifiers="@(Net90RuntimePackRids, '%3B')"

[kotlarmilos]

This PR introduced Net110RuntimePackRids with new RIDs and updated NetCoreRuntimePackRids to reference Net110RuntimePackRids. Because of that, we had to update .NET 10 Microsoft.NETCore.App to reference Net100RuntimePackRids instead. This change should not affect the functionality of .NET 10. What regression did you experience?

[akoeplinger]

@MichaelSimons the change is correct, but it's possibly causing some weirdness because we're still in this 11.0-but-actually-10.0-version state. we should take a closer look at what error it's causing in SB