fix(tests): huge.spec.ts is not running in CI and fails when included

[eugenioenko]

Summary

The huge.spec.ts large file e2e test is effectively dead — it never runs in CI, and when you try to run it, it fails.

Problems

1. Never runs in CI

The CI workflow hardcodes PLAYWRIGHT_TESTS_TO_RUN: roundtrip in reusable_build-and-test.yaml:217, so huge.spec.ts is never executed.

2. appUrl is undefined

PR #920 introduced await page.goto(\${appUrl}?segmentBatchSize=2&maxConcurrentSegmentBatches=1`)in bothhuge.spec.tsandroundtrip.spec.ts, but appUrlis never defined or imported. This causes the navigation to go to"undefined?..."` which breaks the test.

3. Timeout when included in roundtrip

When the large file test is manually copied into roundtrip.spec.ts, it fails with a 10s timeout because the roundtrip config doesn't use the extended 900s timeout that huge.spec.ts gets when PLAYWRIGHT_TESTS_TO_RUN includes huge:

Test timeout of 10000ms exceeded.

Error: download.path: canceled

  > 128 |   const cipherTextPath = await download.path();

The 3 GB encrypt/decrypt needs the 15-minute timeout, but the Playwright config only extends timeouts when it sees huge in PLAYWRIGHT_TESTS_TO_RUN.

Context

Discovered while reviewing #922 (memory leak fix for large browser decrypts). The huge test is the only e2e coverage for large file decrypt, and it would have caught the memory leak if it were actually running.