fix(clients): resolve Node client lock platform entries

The three Node client lockfiles carry their platform binding packages as
bare `{"optional": true}` stubs, with no version, resolved URL, or
integrity hash. npm tolerates that only while the declared version is
unpublished, so `npm ci` passed throughout the v0.23.0 candidate window
and started failing the moment the release published the packages:

  npm error `npm ci` can only install packages when your package.json
  and package-lock.json are in sync ... lock file's
  @registrystack/evidence-client-darwin-arm64@ does not satisfy
  @registrystack/evidence-client-darwin-arm64@0.23.0

Regenerate the three locks against the published registry so each
platform entry carries its version, resolved URL, and integrity hash
again. Only those nine entries change; no other dependency moves.

Signed-off-by: Jeremi Joslin <jeremi@joslin.fr>

Author: jeremi