CSS: six css cases panicked only because less-loader's `import("less")`
hard-panics Deno's vm (same root cause as test/cases/loaders/less-loader).
Inject the CJS less on Deno too (as already done for Bun) and un-skip them:
css-auto, css-loader, import, local-ident-name, prefer-relative-css-import,
source-map-export-types. The remaining css skips emit ESM `.mjs` run through
node:vm SourceTextModule, which Deno aborts on — document that precisely.

Worker: the worker_threads cases un-skipped in the previous commit emit async
"Module not found" errors that leak across cases in the in-band Deno run
(e.g. worker-public-path's path bleeding into later worker tests), so they are
flaky in aggregate though each passes alone. Re-skip blob, custom-worker,
issue-17489, node-worker-async-node, web-worker and output/worker-public-path.

…panic

Root cause of almost every Deno skip: Deno 2.8.3 hard-panics ("Module not
found", bindings.rs) the instant `import.meta` is accessed inside a
vm.SourceTextModule — no initializeImportMeta shape avoids it. webpack's ESM
output reads `import.meta.url` (auto publicPath, createRequire, __dirname), so
every ESM/universal/css/html/node case aborted the whole in-band run.

- Rewrite `import.meta` to a prepended object in the ESM runner under Deno
  (test/harness/runner/rewriteImportMeta.js, parsed via acorn so only real
  meta-properties are touched, never string/comment text). Node/Bun keep the
  initializeImportMeta callback.
- Extend the existing Bun CJS-`less` workaround to Deno for the less-loader
  cases (css-*, layer/*), whose `import("less")` also panics Deno's vm.
- Give worker/worker-self-reference-global a findBundle (its [name].js output
  never matched the default bundle0.js; it only runs where a global Worker
  exists, i.e. never on Node).
- Swallow a fake worker's late post-terminate error so it can't fail a later
  case.

This un-skips ~100 cases. The remaining Deno skips are the few web
worker_threads cases whose in-worker chunk load rejects asynchronously with a
blob:/data:/custom-publicPath URL Deno can't map, leaking into a later case.

--unstable-node-globals, --unstable-bare-node-builtins and --unstable-detect-cjs
were required when the Deno CI was first added; Deno 2.8.3 makes them
default/no-ops for this workload (CJS require resolves bare node builtins, Node
globals are present, CJS is auto-detected). The full test:deno scope passes
without them: basictest 15735, longtest 15554, test+unittest 52953 — zero
failures from removing each flag or all three.

…ation

A Deno worker's globalThis.location is a read-only "data:text/javascript," (the
eval-worker URL), so createFakeWorker's `self.location = new URL(...)` was
silently ignored and webpack derived a bogus "data:text/" publicPath, making
in-worker chunk loads miss and leak an uncaught error into a later case. Use
Object.defineProperty to actually override it (Node/Bun accept either). Also
handle the expected worker load error in output/worker-public-path (its worker
URL is the intentionally-fake workerPublicPath).

This un-skips the last 8 Deno-skipped cases: worker/{blob,custom-worker,
issue-17489,self-import,web-worker,worklet}, trusted-types/web-worker and
output/worker-public-path. The eval-worker bootstrap is CJS and Deno's node-ESM
output uses bare builtins, so restore --unstable-detect-cjs and
--unstable-bare-node-builtins (--unstable-node-globals stays dropped).

…ort map

webpack's node-target ESM output imports builtins bare (e.g. `import "fs"`),
which Deno resolves only with --unstable-bare-node-builtins. Map every bare node
builtin to its `node:` specifier via an import map instead, dropping that flag.
--unstable-detect-cjs stays: Deno needs content-based CJS detection for webpack's
mixed `.js` output (a forced package.json "type":"commonjs" breaks ESM-syntax
`.js` library outputs). Verified: basictest 15867 passed, 0 failures.

Keep every issue/PR template section and the commit description body compact by
default, expanding only when the task's complexity needs it.

Route Deno's eval-worker bootstraps and CJS `.js` worker entries through
temporary `.cjs` files in a worker_threads monkeypatch, so the test suite runs
with zero unstable flags (was --unstable-detect-cjs).

The assertion used a 100ms wall-clock budget; its only real failure mode is an
exponential async-DAG regression that hangs, so a loaded CI runner could starve
microtasks past 100ms and flake. Raise the budget to 2000ms, which still catches
the hang.