feat: Provision independently pinned npm with managed Node (#14437)
## Summary
Advance [TURBO-6325](https://linear.app/vercel/issue/TURBO-6325), the
differing-pin portion of TURBO-6278.
- Factor the concrete pnpm registry preparation/staging core and retain
pnpm's public API and existing behavior.
- Provision independently pinned npm with exact package/version/bin
validation, mandatory SHA-512 and locked SHA-256 verification, and full
resource preservation.
- Bind npm/npx launchers to selected managed Node in the same complete
installation generation, including fresh preparation, healthy reuse, and
stale-shim repair.
```text
independent npm lock + selected Node
-> shared verified registry core
-> complete npm resource tree and bound launchers
-> caller reconciles the full cohort once
```
No hooks, dependency installation, probes, or global Node/Corepack
lookup. Node must not concurrently own npm/npx. Matching Node-bundled
npm remains TURBO-6326; Windows/musl promotion, real npm execution
compatibility, and CLI wiring remain unqualified. TURBO-6278 is not
complete.