ci(test-web): drop npm cache restore — setup-node was burning 4m41s

The Forgejo Actions cache server at 172.18.0.27:41161 isn't reachable
from the test-web runner container; setup-node sat there waiting for
ETIMEDOUT each run. Drop `cache: 'npm'` so the step finishes in seconds.

`npm ci` still works deterministically from package-lock.json — net cost
is ~10-30s of registry fetch vs. 4m41s of timeout. Restore the cache
option once the runner-host network reaches the cache server (separate
operator task).

.forgejo/workflows/test-web.yml

@@ -29,11 +29,16 @@ jobs:
         uses: actions/checkout@v4
 
       - name: Setup Node
+        # `cache: 'npm'` removed — the Forgejo Actions cache server at
+        # 172.18.0.27:41161 isn't reachable from this runner's container,
+        # so setup-node spent 4m41s burning the npm cache restore on
+        # ETIMEDOUT before failing open. npm ci still works deterministically
+        # from package-lock.json; just re-fetches from the registry on each
+        # run. Restore the cache option once the runner-host network reaches
+        # the cache server.
         uses: actions/setup-node@v4
         with:
           node-version: '22'
-          cache: 'npm'
-          cache-dependency-path: web/package-lock.json
 
       - name: Install deps
         run: npm ci