[wasm] Fix WebSocket failures on wasm test runs

[mkhamoyan]

OuterLoop tests that are disabled still are running when /p:TestScope=outerloop.
Xharness ignores -notrait category=failing and runs tests cases marked with SkipOnPlatform,ActiveIssue

Fixes #102157

[mkhamoyan]

/azp run runtime-libraries-mono outerloop

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[mkhamoyan]

/azp run runtime-libraries-mono outerloop

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[pavelsavara]

Could you please also fix all the PlatformNotSupportedException in the outer loop ?

[mkhamoyan]

/azp run runtime-libraries-mono outerloop

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[mkhamoyan]

/azp run runtime-libraries-mono outerloop

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[mkhamoyan]

/azp run runtime-libraries-mono outerloop

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[mkhamoyan]

I find out that -trait and -notrait are respected when passing with outerloop attribute

[OuterLoop("Resource-intensive due to parallel processing", ~TestPlatforms.Browser)]
[SkipOnPlatform(TestPlatforms.Browser, "Not supported on browser")]

but ignored when passed like

[OuterLoop]
[SkipOnPlatform(TestPlatforms.Browser, "Not supported on browser")]

There are 2 ways to go

1. One solution is to update these test cases to skip on wasm from outerloop attribute. (This is implemented in this PR).
2. Fix it in dotnet/arcade repo, I opened a ticket for it Tests marked with OuterLoop attribute ignore -notrait category=failing arcade#14779

@lewing @pavelsavara what do you think ?

[mkhamoyan]

/azp run runtime-libraries-mono outerloop

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[mkhamoyan]

All test cases throwing PlatformNotSupportedException are now disabled.
System.Linq.Expressions.Tests, System.Linq.Parallel.Tests, System.Threading.Tasks.Parallel.Tests, System.Threading.Tasks.Tests are failing because of timeout

Tests timed out after 1800secs
XHarness exit code: 70 (TIMED_OUT)

[akoeplinger]

The underlying problem is this xharness issue: dotnet/xharness#908

The PR looks good to me, though maybe we should also spend some time to actually fix xharness instead?

[mkhamoyan]

I'll merge this to reduce pipeline noise until we fix xharness.