Lighthouse E2E tests fail on Windows (permissions)

[matejchalk]

E2E tests for plugin-lighthouse are failing on Windows.

   FAIL  tests/collect.e2e.test.ts > PLUGIN collect report with lighthouse-plugin NPM package > should run plugin over CLI and creates report.json
  Error: Runtime error encountered: EPERM, Permission denied: \\?\C:\Users\RUNNER~1\AppData\Local\Temp\lighthouse.57724617 '\\?\C:\Users\RUNNER~1\AppData\Local\Temp\lighthouse.57724617'
  Error: EPERM, Permission denied: \\?\C:\Users\RUNNER~1\AppData\Local\Temp\lighthouse.57724617 '\\?\C:\Users\RUNNER~1\AppData\Local\Temp\lighthouse.57724617'
      at rmSync (node:fs:1236:18)
      at Launcher.destroyTmp (file:///D:/a/cli/cli/tmp/e2e/plugin-lighthouse-e2e/node_modules/chrome-launcher/dist/chrome-launcher.js:367:9)
      at Launcher.kill (file:///D:/a/cli/cli/tmp/e2e/plugin-lighthouse-e2e/node_modules/chrome-launcher/dist/chrome-launcher.js:349:14)
      at Object.kill (file:///D:/a/cli/cli/tmp/e2e/plugin-lighthouse-e2e/node_modules/chrome-launcher/dist/chrome-launcher.js:39:18)
      at runLighthouse (file:///D:/a/cli/cli/tmp/e2e/plugin-lighthouse-e2e/node_modules/lighthouse/cli/run.js:217:21)
      at async runLighthouseForUrl (file:///D:/a/cli/cli/tmp/e2e/plugin-lighthouse-e2e/node_modules/@code-pushup/lighthouse-plugin/src/lib/runner/runner.js:44:26)
      at async file:///D:/a/cli/cli/tmp/e2e/plugin-lighthouse-e2e/node_modules/@code-pushup/lighthouse-plugin/src/lib/runner/runner.js:18:38
      at async file:///D:/a/cli/cli/tmp/e2e/plugin-lighthouse-e2e/node_modules/@code-pushup/lighthouse-plugin/src/lib/runner/runner.js:12:28
      at async file:///D:/a/cli/cli/tmp/e2e/plugin-lighthouse-e2e/node_modules/zod/v4/core/schemas.js:1844:28
      at async executeRunnerFunction (file:///D:/a/cli/cli/tmp/e2e/plugin-lighthouse-e2e/node_modules/@code-pushup/core/src/lib/implementation/runner.js:39:20)

Re-running the job doesn't fix this error. The Lighthouse tests have been failing regularly since #1116 was merged. Updating our Node version will have invalidated the Nx cache, so this PR may not be the real cause of the problem.