WASM: Enable Invariant.Tests

[safern]

Contributes towards: #38422

[Dotnet-GitSync-Bot]

I couldn't figure out the best area label to add to this PR. If you have write-permissions please help me learn by adding exactly one area label.

[safern]

Alright, Browser leg is now green.

[SamMonoRT]

@safern @naricc trying to understand why we don't see the Interpreter lanes for runtime tests, we do see the other Mono Prio0 runtime test lanes for jit though

[ghost]

Tagging subscribers to this area: @tarekgh, @safern, @krwq
See info in area-owners.md if you want to be subscribed.

[safern]

It is because in order to optimize resources and avoid dedicating a machine to invoke helix to run the interpreter tests and one for non-interpreter tests, we use the same lane for both and just send to helix jobs with different environment variable settings.

 Starting Azure Pipelines Test Run Mono Linux arm64 Release @ (Ubuntu.1804.Arm64.Open)Ubuntu.1804.Armarch.Open@mcr.microsoft.com/dotnet-buildtools/prereqs:ubuntu-18.04-helix-arm64v8-a45aeeb-20190620155855
  Starting Azure Pipelines Test Run Mono Linux arm64 Release interpreter @ (Ubuntu.1804.Arm64.Open)Ubuntu.1804.Armarch.Open@mcr.microsoft.com/dotnet-buildtools/prereqs:ubuntu-18.04-helix-arm64v8-a45aeeb-20190620155855

You can find that under:
Mono Pri0 Runtime Tests Run Linux arm64 release

In Send to helix step.

So basically on the same lane we run both, JIT and interpreter by creating multiple Helix jobs. Which results in using less machines for our build 😄

[naricc]

@SamMonoRT

@safern @naricc trying to understand why we don't see the Interpreter lanes for runtime tests, we do see the other Mono Prio0 runtime test lanes for jit though

We moved the interpreter to be a scenario instead of a seperate lane. So the interpreter is running, along with the jit, as part of this one "Mono Common Pri0 Test Build AnyOS AnyCPU release". I just double checked to verify it is still running the interpreter.

[safern]

Badges didn't update, build is green.