Disable more tests for interpreter

[janvorli]

Disable one part of the aliasing_retbuf that uses pinvoke with marshalling, fix disabling of calli_excep test that needs to be disabled on the project level as it is executed as isolated and finally Test_HndIndex_10_Reordered that has the same issue as previously disabled Test_HndIndex_10_Plain.

[dotnet-policy-service]

Tagging subscribers to this area: @BrzVlad, @janvorli, @kg
See info in area-owners.md if you want to be subscribed.

[Copilot]

Pull Request Overview

This PR disables several test cases that are incompatible with the CoreCLR interpreter by adding appropriate skip attributes and conditional checks. The changes address three specific test scenarios: an aliasing_retbuf test that uses pinvoke with marshalling, a calli_excep test requiring native exception interop, and Test_HndIndex_10_Reordered which has similar issues to its plain variant.

• Adds SkipOnCoreClrAttribute with InterpreterActive mode to IL test files
• Sets InterpreterIncompatible property at project level for isolated test execution
• Wraps incompatible code section with runtime check for interpreter

Reviewed Changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
Test_HndIndex_10_Reordered.il	Adds skip attribute to disable test when interpreter is active
Test_HndIndex_10_Plain.il	Adds skip attribute to disable test when interpreter is active
calli_excep.ilproj	Sets InterpreterIncompatible flag and adds TestLibrary reference
calli_excep.il	Adds assembly references for skip attribute and test utilities
aliasing_retbuf.csproj	Adds TestLibrary project reference
aliasing_retbuf.cs	Wraps incompatible pinvoke code with interpreter runtime check

[davidwrighton]

Should we have a check for SupportsPInvokeMarshalling instead of the generic interpreter check? You seem to have found a bunch of them.

[janvorli]

Should we have a check for SupportsPInvokeMarshalling instead of the generic interpreter check? You seem to have found a bunch of them.

This is one of the things covered by the issue that the url in the message for disabling points to. There are about 10 different things that the issue describes as "we won't likely implement them now". I would prefer not breaking it down to individual "SupportsXYZ" yet.