[wasm] Disable failing runtime tests

[radical]

Interop/PInvoke/Vector2_3_4/ tests are failing as they depend on native test libraries. But
wasm build for runtime tests does not support that yet.

Issue: #93669

[ghost]

Tagging subscribers to this area: @directhex
See info in area-owners.md if you want to be subscribed.

Issue Details

---

null

Author:	radical
Assignees:	-
Labels:	NO-MERGE, NO-REVIEW, arch-wasm, area-Infrastructure-mono
Milestone:	-

[radical]

@jkoritzinsky @trylek IIUC, excluding tests uses the paths specified in issues.targets. For a test like Interop/PInvoke/Vector2_3_4, a BasicTestMethod is used which uses the full method name to the filter's ShouldRunTest, and that won't match the path from issues.targets. If that is correct, then what is the recommended way of excluding such tests?
I see there is support for a dotnet-test like filter expression, but is that for manual runs?

There are existing exclusions for this like

runtime/src/tests/issues.targets

Lines 2630 to 2632 in a40db02

	<ExcludeList Include="$(XunitTestBinBase)/Interop/PInvoke/Vector2_3_4/Vector2_3_4/**">
	<Issue>https://github.com/dotnet/runtime/issues/82859</Issue>
	</ExcludeList>

.. but these do not work any more, AFAIU!

Update: There might be other similar exclusions which are not effective now, and I guess not needed either? There is another instance of the above for <ItemGroup Condition="'$(TargetArchitecture)' == 'wasm' or '$(TargetsAppleMobile)' == 'true'">.

cc @steveisok

[radical]

cc @lewing

[jkoritzinsky]

Please use the PlatformSpecific attribute or one of the other xunit/XunitExtensions attributes instead of issues.targets for merged tests like this.

[jkoritzinsky]

We should probably also disable these tests on the mobile platforms (all xharness platforms currently have the same infra limitations).

[radical]

We should probably also disable these tests on the mobile platforms (all xharness platforms currently have the same infra limitations).

@steveisok @SamMonoRT do you know if these tests fail for ios, and other platforms? Look for Interop/PInvoke/Vector2_3_4/Vector2_3_4/** in src/tests/issues.targets, it is disabled for a few combinations.
If these tests are not failing on those platforms, then we can simply remove the exclusion. If they are failing, then we can add to the ActiveIssue for these.

This can be done in a follow up PR.