ci(e2e): Run E2E tests without restoring the monorepo's node_modules

[mydea]

Each E2E job restored the full ~860 MB root dependency cache and the build output (about 33s per job, ~2.5 runner-hours per CI run) only to run a few tsx scripts and to resolve the linked @sentry-internal/test-utils. E2E jobs now only download tarballs.

The blocker was test-utils: apps depend on it via link:, so its imports (express, ws) resolved from the monorepo's root node_modules. It is now packed like the SDK packages and pinned through the pnpm overrides the E2E setup already writes, so app package.json files stay unchanged and pnpm installs its dependencies into each app. It goes into its own artifact so it can't end up among the release tarballs.

The E2E scripts are now plain .mjs files without dependencies. They run under each app's pinned Node (down to 20.19), which rules out Node's type stripping. With run.ts converted too, the package no longer needs tsx, dotenv, glob, esbuild or a tsconfig (lint:ts never ran in CI).

Since #25380 the Playwright install reads its version from the app's package.json, so it doesn't need the root node_modules either. aws-serverless still downloads the build output, since its Lambda stack installs the built package directories.

This also fixes the on-failure dump normalization step, which has never matched anything in CI: it searched the repo's test-applications/ while apps run in the runner's temp directory.

Stacked on #25384.

🤖 Generated with Claude Code

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit d16ed93. Configure here.}