Add optional TypeScript runtime support

[noise64]

• implements GOL-220 with opt-in strip-only and transform-capable TypeScript runtime features
• adds Node 22.14-compatible module.stripTypeScriptTypes, TypeScript module loading, feature reporting, and node_modules rejection behavior
• applies the selected strip/transform mode to module files and inline wasm-rquickjs:execution jobs across P2 and P3
• preserves the default component footprint for users who do not enable TypeScript; measured raw P2 Wasm grows from 4.68 MB to 8.06 MB when enabled
• removes a redundant TypeScript transform from ESM graph classification and covers disabled, size-limit, async-entry, strip-only, transform, and latency behavior
• updates README guidance, DTS goldenfiles, and the generated Node compatibility inventory

Node compatibility

• primary CI-enforced: 3228/4425 (72.9%) → 3236/4425 (73.1%)
• full public: 3228/5750 (56.1%) → 3236/5750 (56.3%)
• module: 120 passing / 34 gaps → 129 passing / 25 gaps
• util: 89 passing / 8 gaps → 88 passing / 9 gaps, honestly classifying transformed TypeScript call-site source-map remapping as unsupported
• enables all nine Node 22.14 test-module-strip-types subtests; remaining TypeScript CLI fixtures retain precise process.execPath/flag-emulation deferrals

Validation

• focused P2 and P3 TypeScript runtime tests
• P2 and P3 execution isolation tests
• 9/9 Node stripTypeScriptTypes compatibility cases
• focused P2/P3 test-util-getcallsites verification: 12 passed, 1 explicit source-map gap
• generated compatibility report and TypeScript DTS goldenfiles
• all-targets build, formatting, workspace clippy, Prettier, ESLint, and TypeScript build
• independent Codex review and authorized Claude review; Claude remediation re-review verdict: clear

[noise64]

Let's follow the grouping style already used here, and for the swc deps

[noise64]

Are these okay to be not pinned? What are the guarantees defined by swc project versioning

[noise64]

Let's revisit if this is reasonable / needed constraint.