Upgrade SDK to 9.0.0-rc2

[am11]

No description provided.

[dotnet-policy-service]

Tagging subscribers to this area: @dotnet/runtime-infrastructure
See info in area-owners.md if you want to be subscribed.

[am11]

Looks like this version https://www.nuget.org/packages/runtime.win-x86.Microsoft.DotNet.ILCompiler/9.0.0-rc.2.24473.5
is not present in https://dev.azure.com/dnceng/public/_artifacts/feed/dotnet10/NuGet/runtime.win-x86.Microsoft.DotNet.ILCompiler/versions or https://dev.azure.com/dnceng/public/_artifacts/feed/dotnet9/NuGet/runtime.win-x86.Microsoft.DotNet.ILCompiler/versions

but e.g. x64 one is present https://dev.azure.com/dnceng/public/_artifacts/feed/dotnet9/NuGet/runtime.win-x64.Microsoft.DotNet.ILCompiler/overview/9.0.0-rc.2.24473.4

(same issue with linux-arm (32-bit))

[am11]

Added a temporary workaround d602bf2, we can revert it once we have packages in dotnet9 feed. These are the public versions https://dotnet.microsoft.com/en-us/download/dotnet/9.0, so all packages are expected to be present? cc @mmitche

[am11]

cc @vitek-karas @sbomer for linker test failures (seems like we need to sprinkle a few more [UnconditionalSuppressMessage ("AOT", "IL3050", Justification = "These tests are not targetted at AOT scenarios")] or some such).

[am11]

Added a temporary workaround d602bf2, we can revert it once we have packages in dotnet9 feed. These are the public versions dotnet.microsoft.com/en-us/download/dotnet/9.0, so all packages are expected to be present? cc @mmitche

Looks like win-x86 and linux-arm nupkgs are published to dotnet9 feed, linux-musl-arm need the same treatment. :)

[lewing]

because we do this via arcade #108757 is where this will happen

[am11]

because we do this via arcade #108757 is where this will happen

Since when? Must be new thing I remember doing this by hand in past. But anyway good to know.