Fix Type System Equivalence Checks

[ivdiazsa]

Fixes issue #96242.

This is the initial draft of the solution to address the aforementioned issue. Debugging through Crossgen2 and the compiler for ReadyToRun, we found that on Windows, we were computing and using type identifiers from Guid's, whether there is interop or not. As far as we're concerned, outside of those scenarios we shouldn't need to be doing those checks.

So, initially I want to ask for your guidance more than direct review feedback. Are we approaching this the right way? Is this the right solution? Starting this as draft since this discussion is needed beforehand.

@davidwrighton @jkotas @MichalStrehovsky

[steveisok]

@davidwrighton do you see any harm in backporting this change to net8?

[ivdiazsa]

/azp run runtime-coreclr outerloop

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ivdiazsa]

Failures are known and unrelated. Could we get a review now? @davidwrighton @MichalStrehovsky @lambdageek @kg @steveisok

[steveisok]

LGTM! Only outstanding question I have is if this is backport worthy?

[davidwrighton]

I think this is eligible for backport. It looks reasonable to me.

[ivdiazsa]

I think this is eligible for backport. It looks reasonable to me.

Perfect thanks! Will merge this and start working on the backport PR to .NET 8.

[steveisok]

/backport to release/9.0-rc1

[github-actions]

Started backporting to release/9.0-rc1: https://github.com/dotnet/runtime/actions/runs/10461925315

[steveisok]

/backport to release/8.0-staging

[github-actions]

Started backporting to release/8.0-staging: https://github.com/dotnet/runtime/actions/runs/10461927413

[ivdiazsa]

/backport to release/9.0

[github-actions]

Started backporting to release/9.0: https://github.com/dotnet/runtime/actions/runs/10477927221