test(snapshots): pin dev_engines_runtime_pnpm11 to the seeded default Node version (#2390)

Since 2026-08-08 the Windows PTY snapshot leg fails intermittently on
`dev_engines_runtime_pnpm11`: the `vp dlx -s print-current-version` step
times out after 60s with empty output (13+ runs across branches, main
included, e.g. [run
31302523708](https://github.com/voidzero-dev/vite-plus/actions/runs/31302523708)).
The fixture pinned devEngines node `22.22.2`, the only pin in the suite
that the CI runtime seed does not carry, so the step had to download
Node.js from nodejs.org inside its 60s budget. Connections from the
Windows runner to nodejs.org stall intermittently, and the shared HTTP
client's 2-minute request timeout (see #2386) outlives the step budget,
so a stalled attempt can neither fail nor retry in time. The sibling
`dev_engines_runtime_pnpm10` pins the seeded default `22.18.0` and
passed in ~2s in the same failed runs, which clears the npm registry
path and isolates the stall to nodejs.org.

Pin the pnpm11 fixture to `22.18.0` as well. The `22.22.2` pin carried
no assertion value: #1289 picked it as the then-latest 22.x above vp's
minimum, and the snapshot redacts the printed version to `<version>`.
The case still verifies that vp honors `devEngines.runtime` under pnpm
11. Verified with `cargo test -p vp_cli_snapshots --test cli_snapshots
-- dev_engines_runtime_pnpm11` (passes in 6s, no snapshot drift).

Author: fengmk2

crates/vp_cli_snapshots/tests/cli_snapshots/fixtures/dev_engines_runtime_pnpm11/package.json

@@ -4,7 +4,7 @@
   "devEngines": {
     "runtime": {
       "name": "node",
-      "version": "22.22.2"
+      "version": "22.18.0"
     }
   },
   "packageManager": "pnpm@11.0.6"

crates/vp_cli_snapshots/tests/cli_snapshots/fixtures/dev_engines_runtime_pnpm11/snapshots.toml

@@ -1,6 +1,10 @@
 [[case]]
 name = "dev_engines_runtime_pnpm11"
 vp = "global"
+# The devEngines pin must stay on vp's default Node.js version: the CI seed
+# only carries the default, and any other pin makes this step download a
+# runtime from nodejs.org inside its 60s budget, which times out when the
+# Windows runner's connection stalls.
 steps = [
-  { argv = ["vp", "dlx", "-s", "print-current-version"], comment = "should print Node.js version 22.22.2 from devEngines.runtime", continue-on-failure = true },
+  { argv = ["vp", "dlx", "-s", "print-current-version"], comment = "should print Node.js version 22.18.0 from devEngines.runtime", continue-on-failure = true },
 ]

crates/vp_cli_snapshots/tests/cli_snapshots/fixtures/dev_engines_runtime_pnpm11/snapshots/dev_engines_runtime_pnpm11.md

@@ -2,7 +2,7 @@
 
 ## `vp dlx -s print-current-version`
 
-should print Node.js version 22.22.2 from devEngines.runtime
+should print Node.js version 22.18.0 from devEngines.runtime
 
 ```
 <version>