chore: TypeScript 5.9 (nodenext), NestJS 11, Jest 30

[jrhender]

Summary

Second of five stacked PRs for #57 (stacked on #58).

• TypeScript 4.8 → 5.9 with module/moduleResolution: nodenext and target: es2022. nodenext is what later allows type-checked require() of the ESM-only Credo 0.6+ packages. skipLibCheck added to the root tsconfig (the app and e2e tsconfigs already had it), which also makes the @peculiar/* pins from chore: replace Rush with pnpm workspaces and move to Node 22 #58 unnecessary — removed.
• NestJS 10 → 11 (Express 5): @nestjs/config ^4, @nestjs/typeorm ^11, @nestjs/swagger ^11, @nestjs/axios ^4, @nestjs/serve-static ^5, reflect-metadata ^0.2. Express 5 needs the '{*splat}' middleware wildcard instead of '*', and ConfigModule.forRoot can now return a Promise<DynamicModule>.
• @nestjs/swagger 11 requires additionalProperties on 'object'-typed @ApiProperty declarations; openapi.json regenerated (operationIds gain a _v1 suffix; no path or schema changes).
• Jest 29 → 30 (ts-jest 29.4, @types/jest 30), supertest 7, @types/node 24 declared explicitly in every package to keep a single hoisted copy.

Known follow-up: @nestjs/swagger warns about the duplicate ExchangeResponseDto class name (exchanges vs workflows modules); it becomes an error in swagger v12.

Verification

• Workspace builds; all 68 unit tests and the e2e project pass; app boots, seeds, serves Swagger; middleware wildcard verified against an unknown route (404 logged by HttpLoggerMiddleware)

Part of #57

🤖 Generated with Claude Code