chore(ts): migrate moduleResolution from 'node' to 'bundler'

[danieliser]

Context

PR #1208 silenced the TS 5.x deprecation warning for `moduleResolution: "node"` (deprecated in favor of `node10`/`bundler`/`nodenext`) via `ignoreDeprecations: "5.0"` in `tsconfig.base.json`. That was a deliberate stopgap — an earlier attempt to migrate to `moduleResolution: "bundler"` broke type-root resolution in the pnpm-hoisted monorepo (hoisted `@types/*` weren't findable from package dirs).

Why this matters

TypeScript 7.0 will remove the `ignoreDeprecations` escape hatch entirely. At that point the existing config will refuse to compile. TS 7.0 release timing is uncertain but realistically ~12 months out. Best to fix it on our schedule, not under a deadline.

What's needed

1. Switch `moduleResolution: "node"` → `"bundler"` (recommended for webpack-bundled monorepos) in `tsconfig.base.json`.
2. Resolve the fallout — likely `typeRoots` explicit config or individual package tsconfigs referencing their type dependencies directly.
3. Consider whether `esModuleInterop: false` (also deprecated) should migrate too. Currently kept `false` as a library-consumer compatibility choice.
4. Verify all packages still pass `build:tsc` after the change.
5. Remove the `"ignoreDeprecations": "5.0"` line once migration lands.

Acceptance

• `pnpm run build:tsc` passes across all 21 packages
• No deprecation warnings emitted by TS
• `ignoreDeprecations` no longer needed

References

• PR chore(ts): fix build:tsc pipeline in pnpm monorepo #1208 — stopgap commit: `0723ec9c chore(ts): normalize base tsconfig for pnpm monorepo`
• Background research: TS 5.6 introduced TS5107 deprecation, 7.0 removes the setting entirely