chore: upgrade dependencies (202608)

[mzanoni]

https://trello.com/c/LhBf1a69/21063-recurring-task-development-js-sdk-check-package-dependencies

Summary

• Upgraded direct npm dependencies in packages/client, packages/integrations, and packages/code-analyzer.
• Rolled back packages/client swagger-typescript-api to ^12.0.4 by request, and kept the existing v12 gen-api / gen-api-dev command syntax.
• Ran non-forced npm audit fix for integrations and compatible client dependencies.
• Kept typescript at ^6.0.3: typescript@latest is 7.0.2, but it breaks the current Rollup/TypeScript toolchain and is outside @typescript-eslint/parser@8.65.0 peer range (<6.1.0).
• Skipped comparator-range peer dependency packages/integrations @relewise/client@>=1.22.0-0 <3.0.0 per repository dependency upgrade rules.

Validation

• packages/client: npm --prefix .\packages\client run gen-api passed; generated contract drift was restored because this is not an SDK contract regeneration PR.
• packages/client: npm --prefix .\packages\client run build passed.
• packages/client: npm --prefix .\packages\client test passed (13 suites, 69 tests).
• packages/client: npm --prefix .\packages\client run build:types passed; API Extractor warned that its bundled TypeScript is older than project TypeScript.
• packages/integrations: npm --prefix .\packages\integrations run build passed.
• packages/integrations: npm --prefix .\packages\integrations test passed (1 suite, 2 tests; ts-jest emitted existing deprecated globals config warning).
• packages/integrations: npm --prefix .\packages\integrations run build:types passed; API Extractor warned that its bundled TypeScript is older than project TypeScript.
• packages/code-analyzer: npm --prefix .\packages\code-analyzer run lint passed.
• npm audit: integrations and code-analyzer report 0 vulnerabilities; client reports 4 findings tied to the intentionally rolled-back swagger-typescript-api@12.0.4 chain, where npm's available fix is the v13 upgrade.
• integration tests: not run; credentials were not available and this PR does not change API behavior/contracts.

Notes

• npm outdated only reports TypeScript: current/wanted 6.0.3, latest 7.0.2; this is intentionally not upgraded until the surrounding tooling supports it.