Disable newly added tests on interpreter

[BrzVlad]

Some of the tests timeout when running under coreclr interpreter, which is much slower than jit.

Tests added in #130968

[azure-pipelines]

Azure Pipelines:
Successfully started running 3 pipeline(s).
13 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: @JulieLeeMSFT, @BrzVlad, @janvorli
See info in area-owners.md if you want to be subscribed.

[BrzVlad]

@eiriktsarpalis @krwq I'm wondering if these tests would better be suited as a microbenchmark in dotnet/performance rather than in the library test suite. We would also have better tracking if performance degrades on them.

[Copilot]

Pull request overview

Adjusts System.Private.Xml performance-oriented attribute-duplicate-check tests to be skipped when running under the CoreCLR interpreter, avoiding interpreter-run timeouts while keeping coverage for normal JIT runs.

Changes:

• Converted the affected [Fact] tests to [ConditionalFact(typeof(PlatformDetection), nameof(PlatformDetection.IsNotCoreClrInterpreter))].
• Applied the same condition to the Release-only (#if !DEBUG) variant of the test.

[eiriktsarpalis]

@eiriktsarpalis @krwq I'm wondering if these tests would better be suited as a microbenchmark in dotnet/performance rather than in the library test suite. We would also have better tracking if performance degrades on them.

Agreed.

[BrzVlad]

can we merge this in the meantime to fix CI ?