pnpm 11.0.0-rc.4 on Node.js NPM

Major Changes

Installing a Node.js runtime via node@runtime:<version> (including pnpm env use and pnpm runtime set node) no longer extracts the bundled npm, npx, and corepack from the Node.js archive. This cuts roughly half of the files pnpm has to hash, write to the CAS, and link during installation, making runtime installs noticeably faster. Users who still need npm can install it as a separate package.

pnpm pack-app: replaced the --node-version flag with --runtime, which takes a <name>@<version> spec (e.g. --runtime node@22.0.0). The corresponding pnpm.app.nodeVersion key in package.json was renamed to pnpm.app.runtime with the same syntax. Only node is supported today; the prefix leaves room for future runtimes (bun, deno).
The previous --node-version flag silently inherited from pnpm's global node-version rc setting (which controls which Node runs user scripts), causing the wrong Node build to be embedded in SEAs for users who had that rc key set.

Restored the legacy @pnpm/{macos,win,linux,linuxstatic}-{x64,arm64} npm names for the platform-specific optional dependencies of @pnpm/exe, reverting the scope-nested @pnpm/exe.<platform>-<arch>[-musl] rename from #11316 on the published package names only — the workspace directory layout (pnpm/artifacts/<platform>-<arch>[-musl]/) and the GitHub release asset filenames stay on the new scheme. The rename broke pnpm self-update from v10, which looks up the platform child by its legacy name. linkExePlatformBinary now checks for both schemes so a later rename can ship without a v10-compatibility hazard.