To quash warnings in Node 26.

Picks up the fix for unbounded memory growth when replacing ES modules:
quibble now only re-evaluates modules that are mocked or can reach a mocked
module, instead of every module imported while any mock exists.

td.replaceEsm('some-package') resolves the package through quibble, which
under pnpm can't see packages that only the app depends on unless pnpm
hoisting happens to make them visible (testdouble/quibble#84). The new
examples/node-esm-pnpm project is a pnpm workspace with hoisting off whose
packages/app test replaces is-number, a dependency of that package only.
It has to be a workspace: in a single pnpm project the app's own
node_modules is still within reach of quibble's.

It fails with quibble 0.11.x (the real is-number runs, because quibble
replaces a different copy) and with 0.12.0 on Node 24+ (the generated stub
for a CommonJS module is a SyntaxError), so it's expected to fail until
quibble is bumped to 0.12.1.

script/run-examples installs examples that have a pnpm-workspace.yaml with
pnpm, and CI installs pnpm (8 on Node 16, 9 on Node 18, latest otherwise).
The example sets hoisting off in both pnpm-workspace.yaml (pnpm 10+) and
.npmrc (pnpm 8/9), and minimumReleaseAge: 0 so pnpm doesn't add exclusions
to pnpm-workspace.yaml for just-released dependencies. Its lockfile isn't
committed, so run-examples installs with --no-frozen-lockfile.

Picks up two fixes for replacing ES modules:

- 0.12.0 resolves bare specifiers from the caller instead of from quibble's
  own directory, so td.replaceEsm('some-package') replaces the copy the
  test imports under pnpm, and in monorepos where packages need different
  versions of a dependency (testdouble/quibble#84)
- 0.12.1 generates valid stubs for export names that aren't identifiers,
  so td.replaceEsm() of a CommonJS package no longer fails on Node 24+ with
  "SyntaxError: Unexpected token '.'" (Node gives CommonJS modules a
  'module.exports' named export)

With these, the node-esm-pnpm example passes.

Fix support for pnpm