Regenerate the committed TypeScript client — src/generated is stale vs the current spec

[dougborg]

Problem

The committed packages/katana-client/src/generated/** is out of date relative
to the current docs/katana-openapi.yaml + @hey-api/openapi-ts version. A fresh
npm run generate produces a large content diff (~2,900 lines even ignoring
whitespace: index.ts +1842, sdk.gen.ts +1155, etc.) — new SDK methods/types that
exist in the spec but not in the committed client.

Why CI doesn't catch it

The typescript-client job regenerates fresh and typechecks, but never diffs the
committed output (unlike the Python generated-files job, which fails on any drift).
This is intentional — the TS generator shells out to per-platform native binaries so
its output isn't byte-stable macOS↔Linux, so a drift check would false-positive. The
side effect is that committed staleness is invisible.

Proposed work

• Run npm run generate and commit the refreshed src/generated/**.
• Confirm npm run typecheck + npm test stay green.
• Do this on top of chore(ts-client): format codegen output with Biome, not ambient prettier #976 (which makes codegen deterministic by pinning prettier) so the
  regenerated output is reproducible.

Notes

• Consumers read the committed client without building, so staleness is user-visible
  (missing endpoints/types). Worth doing but not urgent.
• Keep this PR only the regeneration so the diff is reviewable as "codegen output,"
  not mixed with logic changes.