fix(sdks): include source content in sourcemaps

[xxxxxmax]

PR Scope

This is a packaging/source-map fix across SDK packages that publish compiled TypeScript output.

Description

The SDK packages currently emit JavaScript sourcemaps, but published npm packages only include dist. The generated .js.map files reference original TypeScript paths such as ../../../src/index.ts without embedding sourcesContent, so downstream tooling that resolves sourcemaps from the published package can warn that the source files are missing.

This sets inlineSources: true alongside sourceMap: true for the SDK tsconfig.base.json files so generated sourcemaps include the original TypeScript source content. Runtime JavaScript and type declaration output are unchanged; only sourcemap contents change.

How Has This Been Tested?

• bun install --frozen-lockfile
• bun run g:build
• bun run g:lint
• bun run g:typecheck
• Manually inspected generated sourcemaps, including:
  • sdks/sdk-core/dist/esm/src/index.js.map
  • sdks/router-sdk/dist/esm/src/index.js.map
  • sdks/universal-router-sdk/dist/esm/src/index.js.map
  • sdks/v3-sdk/dist/esm/src/entities/pool.js.map

Each inspected map now contains sourcesContent entries.

Are there any breaking changes?

No. This only changes emitted sourcemap metadata and adds source content to the generated .js.map files.

(Optional) Feedback Focus

Please confirm that inlining source content in sourcemaps is preferred over publishing src files or disabling sourcemap emission.