Fix deterministic CI install by syncing lockfile with npm 10 resolution data

[Copilot]

The Deterministic tests workflow failed before tests executed because npm ci rejected package-lock.json as out of sync with package.json in the GitHub Actions runtime (Missing: @noble/hashes@2.2.0 from lock file).
This PR updates the lockfile to match npm 10’s expected dependency graph so clean installs are deterministic again.

• Lockfile synchronization (npm 10 semantics)

  • Regenerated package-lock.json with npm 10-compatible metadata.
  • Added missing nested optional peer entries for @noble/hashes@2.2.0 under packages that declare ^1.8.0 || ^2.0.0.

• Scope of change

  • No application/runtime source changes.
  • Change is limited to dependency resolution metadata in package-lock.json.

"node_modules/jsdom/node_modules/@noble/hashes": {
  "version": "2.2.0",
  "optional": true,
  "peer": true
}

[gemini-code-assist]

Caution

The consumer version of Gemini Code Assist on GitHub has been sunset. All code review activity has officially ceased.