Fix vitest-pool-workers when nodejs_compat is enabled

[petebacondarwin]

Fixes #11028
Fixes #11029

Recent additions to native nodejs_compat modules (node:console and node:vm) broke the vitest-pool-workers as it relies upon specialized polyfills to ensure that the Vitest runner can operate. This broke because generally the vitest-pool-workers uses module fallback to provide the polyfill which no longer works when there is a native version available.

• fixes by putting the polyfill into the bundle directly which overrides the built-in module.
• adds a test that proves that nodejs_compat scenarios work
• changes most vitest-pool-workers fixtures to always use the latest compat date (by adding a feature to vitest-pool-workers where the latest compat date is used if none is provided).

The aim of the last bullet is for us to get an early warning if any changes to the runtime that are flagged behind a compat date will cause breakages to testing.

---

• Tests
  • Tests included
  • Tests not necessary because:
• Public documentation
  • Cloudflare docs PR(s): Clarify compatibility_date usage in configuration cloudflare-docs#25954
  • Documentation not necessary because:
• Wrangler V3 Backport
  • Wrangler PR:
  • Not necessary because: vitest-pool-workers is not backported

[changeset-bot]

🦋 Changeset detected

Latest commit: 134ddad

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[pkg-pr-new]

create-cloudflare

npm i https://pkg.pr.new/create-cloudflare@11047

@cloudflare/kv-asset-handler

npm i https://pkg.pr.new/@cloudflare/kv-asset-handler@11047

miniflare

npm i https://pkg.pr.new/miniflare@11047

@cloudflare/pages-shared

npm i https://pkg.pr.new/@cloudflare/pages-shared@11047

@cloudflare/unenv-preset

npm i https://pkg.pr.new/@cloudflare/unenv-preset@11047

@cloudflare/vite-plugin

npm i https://pkg.pr.new/@cloudflare/vite-plugin@11047

@cloudflare/vitest-pool-workers

npm i https://pkg.pr.new/@cloudflare/vitest-pool-workers@11047

@cloudflare/workers-editor-shared

npm i https://pkg.pr.new/@cloudflare/workers-editor-shared@11047

wrangler

npm i https://pkg.pr.new/wrangler@11047

commit: 134ddad

[vicb]

Do we really need a polyfill for node:url ?

[petebacondarwin]

@vicb I did a pass through and removed all unnecessary polyfills (turning on native features as needed). PTAL.

[vicb]

As discussed offline, using a Set could simplify the handling of the flags in this PR.

I find it hard to figure out what that means:

	ensureFlag(
		runnerWorker.compatibilityFlags,
		"enable_nodejs_tty_module",
		"disable_nodejs_tty_module"
	);

ensure what flag (enable vs disable) is what (used vs not used)?

Maybe a wrapper class could help, constructed with an array, using a Set internally, having ensureUsed(flag) and ensureNotUsed(flag) and a flags getter returning an array

[petebacondarwin]

I reworked the helper to make its purpose more clear: ab1f757