Align dependency versions across workspaces, introduce a version catalog

Deliberately excluded from the monorepo migration (`.scratch/monorepo-migration/spec.md`, "Out of Scope").

eslint, vitest, the Node type definitions, the shared TypeScript configuration and the logger disagree across `apps/jobnik-manager`, `packages/jobnik-sdk`, `packages/jobnik-openapi` and `e2e`. Aligning them is separate work, one pull request per workspace, introducing a pnpm dependency catalog as it goes so future additions and alignments are the same change. The SDK's eslint jump spans two majors of the shared configuration and will be the largest mechanical change.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Start with .scratch/monorepo-migration/spec.md and inspect the dependency manifests and shared TypeScript, ESLint, Vitest, and logger configuration across apps/jobnik-manager, packages/jobnik-sdk, packages/jobnik-openapi, and e2e. Introduce the pnpm dependency catalog while aligning versions, handling the SDK's two-major shared-configuration jump. Done means each workspace has aligned dependencies and the catalog supports future additions.

Written by the indexing model from the issue text.