Fix Cypress workflow failures caused by invalid aws4 lockfile tarballs

[Copilot]

The Cypress workflows were failing during npm install because lockfiles referenced a non-existent aws4 tarball (1.13.3). This updates both affected lockfiles to a published tarball so dependency resolution can proceed in CI.

• Dependency lockfile corrections

  • Updated src/test/e2e/package-lock.json to point node_modules/aws4 at a valid published artifact.
  • Updated src/test/K8s-tests/package-lock.json to point node_modules/aws4 at a valid published artifact.
  • Scope is intentionally limited to the broken lockfile entries used by the failing workflows.

• Why this unblocks the workflows

  • Heroku workflow installs from src/test/e2e; npm resolves from the checked-in lockfile.
  • Minikube/Vault Cypress workflow installs from src/test/K8s-tests; npm resolves from that lockfile as well.
  • Replacing the 404 tarball URLs removes the install-time hard failures.

"node_modules/aws4": {
  "version": "1.13.2",
  "resolved": "https://registry.npmjs.org/aws4/-/aws4-1.13.2.tgz",
  "integrity": "sha512-lHe62zvbTB5eEABUVi/AwVh0ZKY9rMMDhmm+eeyuuUQbQ3+J+fONVQOZyj+DdrvD4BY33uYniyRJ4UJIaSKAfw=="
}

> [!WARNING]
>
>

[commjoen]

@copilot Can you fix https://github.com/OWASP/wrongsecrets/actions/runs/24765415697/job/72460422917?pr=2504 as well?

[Copilot]

@copilot Can you fix https://github.com/OWASP/wrongsecrets/actions/runs/24765415697/job/72460422917?pr=2504 as well?

Fixed in 0f22529. I updated src/test/K8s-tests/package-lock.json to use the published aws4 tarball (1.13.2) so job 72460422917 no longer fails on the npm 404 during npm install.