Quarantine TypeIntrinsics on WASM ReadyToRun

[Copilot]

• Failure: On WASM ReadyToRun, the TypeIntrinsics test can hit a runtime assertion after catching a NullReferenceException.
• Change: Conditionally skip TestEntryPoint in both _r and _ro via the shared ActiveIssue attribute. Non-R2R coverage remains enabled; the runtime defect is unchanged.

• Fixes [wasm/R2R] TypeIntrinsics_r: GC reports uninitialized frame slots during throw-helper calls (pMT->Validate assert) #135966

[azure-pipelines]

Azure Pipelines:
16 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

[dotnet-policy-service]

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

[lewing]

Superseded by #135970, which fixes the root cause. On wasm R2R the JIT skipped prolog zeroing for GC locals stored after a throwing null check (e.g. Object.GetType), so a GC reported stale stack contents. If a quarantine is still needed before #135970 merges, this should reference #135966 instead of "Fixes", so the issue stays open.

Note

This comment was drafted with GitHub Copilot.

[agocke]

@lewing I'm fine with taking that PR right now, but in general we should avoid enabling tests only to mark them Known Build Error. If tests don't pass on the given platform yet they shouldn't be enabled and we shouldn't wait support for the test is implemented.