ci: nuxt runtime-compat harness fails silently on transient npm errors

[mu-hashmi]

Describe the bug

The TypeScript SDK runtime-compat suite's nuxt harness (libs/sdk-typescript/runtime-tests/nuxt/run.sh) can fail with zero diagnostic output:

================================================================
# nuxt
================================================================
[x] nuxt FAIL (3s)

The script runs under set -euo pipefail, removes package-lock.json, then runs npm install --silent. --silent suppresses npm's error output entirely, so a transient registry/network failure exits the script in a few seconds with nothing in the log, and the E2E job fails with no way to tell what happened.

Two occurrences on 2026-06-11 (UTC), both passing on rerun with no code change:

• https://github.com/daytonaio/daytona/actions/runs/27323670138
• second occurrence on the same PR's next push, identical signature

Every other runtime harness in the same suite passed in both runs.

To Reproduce

Transient npm registry failure during the harness's npm install --silent - not deterministically reproducible; the silence is the bug.

Expected behavior

A harness failure should say why it failed. Some combination of:

• drop --silent (or redirect install output to /tmp/nuxt-install.log and dump it on failure, as the runtime log already does),
• use a committed lockfile + npm ci so resolution is deterministic,
• optionally one retry for the install step to absorb registry blips.

Additional context

Fresh npm install without a lockfile also makes this harness the slowest and least deterministic in the suite; the same pattern exists in some sibling harnesses but nuxt is the one that has flaked silently.