fix(ts-client): keep Babel override consistent with lockfile

[neubig]

Problem

TypeScript client CI on current main fails before tests because npm re-resolves the self-referencing @babel/core override beyond the version captured by the lockfile.

Actual Behavior

After the repository setup command uv sync, change into clients/typescript. Both the Node 22.12 and Node 24 CI jobs then fail at:

npm ci

The error begins with:

Invalid: lock file's @babel/core@8.0.1 does not satisfy @babel/core@8.0.5

and then reports the newer Babel dependency graph missing from the lock.

Expected Behavior

A clean install from the committed package manifest and lockfile succeeds reproducibly on every supported Node version.

Acceptance Criteria

• npm ci succeeds from a clean clients/typescript checkout on Node 22.12 and Node 24.
• The fix retains the currently tested Babel 8.0.1 dependency graph; dependency upgrades remain in their dedicated Dependabot PRs.
• No generated client or runtime behavior changes.

[github-actions]

✅ ready-for-dev label applied

This issue meets the readiness criteria and is ready for contribution.
A contributor can now open a PR that links this issue (Fixes #<number>).

This is an automated check — no AI was used to generate this comment.

[onatozmenn]

This looks resolved on current main: npm ci in clients/typescript succeeds cleanly (verified locally), and the lockfile no longer pins the stale 8.0.1 graph — Dependabot #5062/#5061 bumped @babel/core/@babel/preset-env to 8.0.5 with #5073 reconciling after the Vitest migration. Probably safe to close; leaving that call to a maintainer.