chore: move shared dependencies to a pnpm catalog

## Description

Several dependencies are declared in 2+ workspace packages, and some have drifted to different version ranges for the same tool. `typescript` alone spans `^6`, `~6.0.3`, and `^6.0.3` across packages. A pnpm `catalog:` centralizes each version in `pnpm-workspace.yaml` so packages reference `"": "catalog:"` and can't drift.

## Proposed solution

Add a `catalog:` block to `pnpm-workspace.yaml` and point the shared deps at it. Prioritize the drift cases; unify each on a single range.

**Drift today (do first):** `typescript`, `@types/node`, `@types/react`, `@types/react-dom`, `tailwindcss`, `@tailwindcss/postcss`.

**Aligned already (centralize to keep them so):** `@filoz/synapse-sdk`, `react`, `react-dom`, `@tanstack/react-query`, `lucide-react`, `graphql-request`, `clsx`, `sonner`.

## Done criteria

- [ ] `catalog:` block added to `pnpm-workspace.yaml`
- [ ] Drift deps unified on one range and set to `catalog:` across all packages
- [ ] `pnpm install` succeeds; lockfile updated
- [ ] `pnpm build && pnpm type-check && pnpm lint` pass repo-wide

## Notes
Merge the Dependabot PRs first to update the dependencies.

Start with pnpm-workspace.yaml and inspect the workspace package manifests to find the listed shared dependencies and their current version ranges. Review and merge the Dependabot updates first, then centralize the drift and already-aligned dependencies through the catalog. Done means pnpm install updates the lockfile and pnpm build && pnpm type-check && pnpm lint pass repo-wide.

Written by the indexing model from the issue text.