perf pipeline: Switch to node 14.x

[radical]

• Switch to node 14.x instead of 18.x, because the latter doesn't seem
  to be compatible with ubuntu 18.x:
  node: /lib/x86_64-linux-gnu/libc.so.6: version GLIBC_2.28' not found (required by node)`

• remove the existing nodejs package before installing a new
  one, because these machines are shared, and would get affected by
  installations performed by other runs.

• Fix the case where pre-requisites would fail to install, but then helix would exit with exit code 0, and it would "look" as if everything went fine. This was happening because we set _commandExitCode=1, but helix sets this itself based on $?. So, to fix this we exit with (exit 1), and helix should be able to pick that up, thus causing the whole job to fail, as expected

• Install node, and jsvu only for the wasm jobs, as they are not needed by others

[ghost]

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

Issue Details

---

• Switch to node 14.x instead of 18.x, because the latter doesn't seem
  to be compatible with ubuntu 18.x:
  node: /lib/x86_64-linux-gnu/libc.so.6: version GLIBC_2.28' not found (required by node)`

• Also, remove the existing nodejs package before installing a new
  one, because these machines are shared, and would get affected by
  installations performed by other runs.

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

[radical]

/azp run runtime-wasm-perf

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[radical]

/azp run runtime-wasm-perf

[azure-pipelines]

Azure Pipelines failed to run 1 pipeline(s).

[radical]

/azp run runtime-wasm-perf

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[radical]

/azp run runtime-wasm-perf

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[radical]

/azp run runtime-wasm-perf

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[radical]

@DrewScoggins I have a run from this in dotnet-runtime-perf - 20220817.1 . Does that look good? There are some failures on the wasm jobs, but those are related to recent ILLinker changes. I'll fix those.
The other jobs seem to be running too, but I checked only with some random sampling.

[DrewScoggins]

Just the one other comment, other than that LGTM.

[radical]

Opened dotnet/performance#2563, and #74104 for the new failures.

[radical]

And #74088 .

Any objections to merging this right away to unblock the pipeline, since the changes are strictly in performance only files?

[radical]

/backport to release/7.0-rc1

[github-actions]

Started backporting to release/7.0-rc1: https://github.com/dotnet/runtime/actions/runs/2877411794