ILCompiler package used in runtime without ensuring matching framework

[ericstj]

Description

See #106729

When building the product we run on an older shared framework than the last built and consumed runtime.

Reproduction Steps

Build dotnet/runtime when it's using a MicrosoftDotNetILCompilerVersion newer than the dotnet version, and ILC depends on an API change in the framework.

Expected behavior

Build succeeds

Actual behavior

Failure because the tool framework is missing API required by ILC

Regression?

Yes, torn state introduced by #100845

Known Workarounds

No response

Configuration

No response

Other information

No response

[dotnet-policy-service]

Tagging subscribers to this area: @agocke, @MichalStrehovsky, @jkotas
See info in area-owners.md if you want to be subscribed.

[ericstj]

Probably first introduced in #89655 (comment) where @jkotas predicted this problem.

@sbomer