fix(common): remove moduleResolution override in ts-node register (fixes #2025)

[just-jeb]

Problem

When a user sets moduleResolution: "bundler" in their tsconfig.json, the custom-webpack builder was silently overriding it with "node" inside ts-node's register() call. This caused TypeScript to fail resolving packages that are only accessible via the package.json exports field (subpath exports), producing TS2307: Cannot find module errors.

Example: @angular/core/primitives/di has no physical file on disk — it is only accessible via the exports field. With moduleResolution: "bundler" it resolves fine; with "node" it does not.

Reported in #2025.

Root Cause

In packages/common/src/load-module.ts, _tsNodeRegister() passes compilerOptions.moduleResolution: 'node' to ts-node. This overrides whatever the user set in their tsconfig.json, regardless of their intent.

// Before (buggy)
loadTsNode().register({
  project: tsConfig,
  compilerOptions: {
    module: 'CommonJS',
    moduleResolution: 'node',  // <-- BUG: forces node resolution, ignoring user's tsconfig
    types: ['node'],
  },
});

Fix

Remove the moduleResolution override entirely. TypeScript explicitly allows moduleResolution: "bundler" together with module: "CommonJS" — the combination type-checks using bundler resolution semantics (respects exports field) while emitting CommonJS output for the Node.js process.

// After (fixed)
loadTsNode().register({
  project: tsConfig,
  compilerOptions: {
    module: 'CommonJS',   // kept — Angular CLI runs in a CJS process
    // moduleResolution not set — user's tsconfig value is preserved
    types: ['node'],     // kept — gives webpack configs access to Node globals
  },
});

Regression Test

Adds a new bundler-resolution-ts angular.json configuration in full-cycle-app that uses a TypeScript webpack config importing from @angular/core/primitives/di (a subpath export, no physical file). The integration test ts-config-bundler-module-resolution in integration.js verifies that ng build -c bundler-resolution-ts succeeds. This fails before the fix and passes after.

Previously attempted

An earlier iteration replaced ts-node with tsx. This was reverted because tsx uses esbuild for transpilation and skips TypeScript's type checker entirely — a regression for users who choose .ts config files specifically for type safety.

Fixes #2025