Add ios-arm64, iossimulator-arm64, android-arm64, android-x64 to ILCompiler supported RIDs for .NET 11

[Copilot]

NativeAOT cross-compilation to iOS and Android targets fails because the SDK doesn't recognize these as valid ILCompiler target RIDs, even though the corresponding Microsoft.NETCore.App.Runtime.NativeAOT.<RID> packages exist (ios/iossimulator since net8.0, android since net10.0).

• Added ios-arm64, iossimulator-arm64, android-arm64, android-x64 to Net110ILCompilerSupportedRids in GenerateBundledVersions.targets
• Added a macOS-only unit test (NativeAot_publishes_for_ios_arm64_on_macos) that publishes a HelloWorld project for ios-arm64 with PublishAot=true and verifies it succeeds with no warnings

These flow into both ILCompilerSupportedRids and ILCompilerSupportedPortableRids via the existing item group chain, enabling dotnet publish -r ios-arm64 /p:PublishAot=true without requiring workload-specific workarounds.

[agocke]

@simonrozsival for thoughts

[Copilot]

Pull request overview

Updates the SDK’s bundled ILCompiler (NativeAOT) RID allowlist for .NET 11 so cross-compiling to additional iOS and Android targets is recognized as supported, aligning SDK validation with the existence of corresponding NativeAOT runtime packs.

Changes:

• Add ios-arm64 and iossimulator-arm64 to Net110ILCompilerSupportedRids.
• Add android-arm64 and android-x64 to Net110ILCompilerSupportedRids.

[agocke]

@copilot please add a simple unit test that only runs on macOS and publishes for ios-arm64 with PublishAot. It should succeed with no warnings.

[Copilot]

@copilot please add a simple unit test that only runs on macOS and publishes for ios-arm64 with PublishAot. It should succeed with no warnings.

Added in 2e9e0d5. The test uses [MacOsOnlyFact], creates a HelloWorld project with PublishAot=true, publishes with -r ios-arm64, and asserts .Pass() with no warnings in stdout or stderr.