The `require(esm)` "module.exports" interop test now cross-checks
webpack's bundled output against Node.js's native result by shelling
out to a child `node` process — Jest's runtime intercepts every
`require()` in-process (even via `Module.createRequire`), so the
comparison has to run outside it. The test also keeps a literal
`require(/* webpackIgnore: true */ … )` in the entry to assert webpack
preserves the comment in the emitted bundle.

A `test.filter.js` skips the case on Node versions older than 22.12.0,
where `require(esm)` is not unflagged.

`.js` fixtures are renamed to `.mjs` so the child `node` process parses
them as ES modules.

…ison

Replaces the child-process approach with a `webpackIgnore: true` comment
on the native side. Webpack leaves the call literal, and at runtime a
new `test.config.js` short-circuits the absolute paths via
`testConfig.modules` to values pre-loaded through Node's `Module._load`
(which, unlike `Module.createRequire`, Jest does not intercept).

The webpack-bundled `require("./*.mjs")` and the
`require(/* webpackIgnore: true */ pathVar)` calls thus go through two
independent paths and their results are compared, with no child
processes.

Adds two fixtures and corresponding cases that pin down behaviors the
Node.js docs guarantee but the previous tests did not exercise:

  * `"module.exports"` wins over a sibling `default` (and any other named
    export). The unwrapped value is just the binding — `default` /
    `named` are not visible on it.
  * `export { x as "module.exports" } from "./other"` still unwraps when
    required from CJS.

Both cases are cross-checked against `Module._load`'d native values.

`CommonJsExportRequireDependency` (the dependency behind
`module.exports = require(…)`, `module.exports.foo = require(…)`,
`exports.bar = require(…).baz`) now applies the same Node.js `require(esm)`
unwrap as plain `require()` / `require().foo`. When the imported module
is an ES module with a `"module.exports"` named export:

* `getReferencedExports` reports only `"module.exports"` as referenced;
  further property access in `ids` lands on the unwrapped value which
  webpack does not model.
* `getExports` prepends `"module.exports"` to the export chain when a
  single name is being re-exported, and falls back to `exports: true`
  (canMangle: false) for full re-exports — the unwrapped value's own
  properties cannot be enumerated statically.
* The template emits `__webpack_require__(id)["module.exports"]<ids>`
  in place of `__webpack_require__(id)<ids>`.

Three new fixtures cover the wrapper-CJS shapes against Node's real
`Module._load` result.

This change brings webpack into line with Node.js's documented
`require(esm)` semantics, so it's a fix for divergent behavior rather
than a new feature — patch is the right semver bucket.