fix: sync server.json version metadata with package.json

[syf2211]

Summary

Sync server.json registry metadata with package.json and add CI guardrails so version drift does not recur.

Motivation

Fixes #235. The repo's server.json had drifted far behind package.json and npm (3.7.5 / 3.22.1 vs 3.22.2). The publish workflow already synced versions at publish time for the MCP registry, but those updates were never committed back to the repository.

Changes

• Update server.json top-level version and npm package entry to 3.22.2
• Add scripts/sync-server-json.mjs and scripts/check-server-json-version.mjs
• Add pnpm run sync:server-json and pnpm run check:server-json
• Run the check in CI after build
• Reuse the shared sync script in the publish workflow

Tests

From repo root:

pnpm install
pnpm run build
pnpm run check:server-json
pnpm run sync:server-json

All passed locally.

Notes

When bumping package.json version, maintainers should run pnpm run sync:server-json and commit the updated server.json alongside the bump. CI will fail if they forget.

Fixes #235