Two fixes for running the release/10 test suite under pnpm 12.
registry-mock's useNodeVersion option starts verdaccio with
`pnpm --use-node-version=<version> exec node`. release/10 now runs its
tests under pnpm 12, which removed --use-node-version, so every package
that uses the mock registry failed in the jest global setup. The setup
now resolves Node.js 20.16.0 through `pnpm dlx node@runtime:20.16.0` and
puts it first on the PATH of the `node` registry-mock spawns.
registry-mock 6 makes the same switch to pnpm dlx, but it is ESM-only
and this CommonJS setup cannot require it on Node.js 18 and 20.
preparePackage runs `pnpm install` in a git-hosted dependency, and the
tests got whichever pnpm was on PATH. pnpm 12 refuses the v5.4 lockfile
of the prepare-script fixtures in CI instead of converting it. As on
main (#10317), the jest setup now puts the pnpm built from this
repository first on PATH.
Zoltan Kochan
f72f4c8c97