[wasm] Don't fail the CI job if Firefox tests fail in runtime-wasm

[radical]

Debugger tests running on Firefox are known to be unstable right now. So, they can fail on unrelated PRs.
When they are run on runtime-staging, the test failures don't mark the whole job as failed.
But when they run on runtime-wasm, they do. And this shows up as failed in GitHub checks view, which is not helpful.

[ghost]

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

Issue Details

---

.. since they are known to be unstable currently. Having the Firefox job be red because some tests failed is not useful, because it can happen on any PR that runs runtime-wasm pipeline, and is not useful information.

Author:	radical
Assignees:	-
Labels:	area-Infrastructure-mono
Milestone:	-

[ghost]

Tagging subscribers to 'arch-wasm': @lewing
See info in area-owners.md if you want to be subscribed.

Issue Details

---

.. since they are known to be unstable currently. Having the Firefox job be red because some tests failed is not useful, because it can happen on any PR that runs runtime-wasm pipeline, and is not useful information.

Author:	radical
Assignees:	radical
Labels:	arch-wasm, area-Debugger-mono
Milestone:	-

[radical]

/azp run runtime-wasm

[azure-pipelines]

Azure Pipelines failed to run 1 pipeline(s).

[radical]

/azp run runtime-wasm

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[radical]

/azp run runtime-extra-platforms

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[radical]

/azp run runtime-wasm,runtime-extra-platforms

[azure-pipelines]

Azure Pipelines failed to run 2 pipeline(s).

[radical]

/azp run runtime-wasm,runtime-extra-platforms

[azure-pipelines]

Azure Pipelines successfully started running 2 pipeline(s).

[radical]

The unrelated AOT build failure is likely #69653 .
I cancelled the manual pipelines, once I confirmed that the fix still works.

[jakobbotsch]

@radical I'm seeing libraries test runs show up as "!" in AzDO on failures and being reported as succeeded on GitHub. For example, my change at #68703 has many failures in "runtime-coreclr libraries-pgo", yet it does not show up as failed on GitHub. Seems related to this change?

[radical]

I'm looking at that right now. If I don't figure out a solution soon, then I'll revert it.

[radical]

@jakobbotsch #69736