ci: backport ci-deploy fixes to release + release-verify

Two CI fixes had been applied to ci-deploy.yml but never propagated:

1. release-verify.yml: install Playwright browsers before e2e
   `pnpm install --frozen-lockfile` only fetches the npm package; the
   chromium binary needs `playwright install --with-deps`. Without this
   the e2e step fails on a fresh runner with "browser not found".
   (mirrors ci-deploy commit 6e7e931)

2. release.yml: exclude tests/eslint/** from the paranoid `pnpm test`
   typescript-eslint's project cache doesn't see runtime-generated
   probe files inside the runner container, so those config-drift
   guards pass locally but fail CI-only — same reason ci-deploy uses
   the exclude flag. (mirrors ci-deploy commit 3fccd8e)

Other ci-deploy specifics (pve-201 concurrency, /api pre-warm + tunnel
diagnostics, CI_DEPLOY=1 quarantine env) intentionally stay ci-deploy-
only: release-verify runs the full suite by design, and the other
fixes are tied to ci-deploy's host/build path.

.gitea/workflows/release-verify.yml

@@ -36,6 +36,10 @@ jobs:
         id: wait_customer
         run: scripts/ci/wait-for-url.sh http://flights-ui.devwebzavod.ru/ru-ru/onlineboard 60 5
 
+      - name: Install Playwright browsers
+        id: playwright_install
+        run: pnpm exec playwright install --with-deps chromium
+
       - name: Run Playwright e2e against customer URL
         id: e2e_customer
         env:

.gitea/workflows/release.yml

@@ -60,10 +60,13 @@ jobs:
 
       - name: Paranoid re-run — typecheck + lint + unit
         id: paranoid
+        # Mirror ci-deploy's `--exclude 'tests/eslint/**'`: typescript-eslint's
+        # project cache doesn't see runtime-generated probe files inside the
+        # runner container, so those config-drift guards fail CI-only.
         run: |
           pnpm typecheck
           pnpm lint
-          pnpm test
+          pnpm test -- --exclude 'tests/eslint/**'
           pnpm test:ci
 
       - name: Clone GitLab target