feat(mcp-server): restore the remote MCP server package

[hacker-cb]

Restores @1c-odata/mcp-server — a clean revert of #162's squash commit (4c57cdb). The package comes back exactly as removed: the whole packages/mcp-server/ tree, CI gates 2c/2d/8b, the deploy-pg-smoke / deploy-package-smoke jobs, deploy-compose.yml, release-image.yml + the publish-image job in release.yml, the Dependabot docker/docker-compose entries and better-auth exclusions, the root .dockerignore, the deploy/ci Biome override, and the mcp-server changesets (the fixed group is five packages again).

🅿️ Parked on purpose — do not merge. The server needs more bake time before its first npm release. This PR exists so the implementation stays visible, reviewable, and one rebase away from landing.

Verified on this branch: biome ci, turbo typecheck, test:unit, test:integration:offline, test:e2e (including the restored mcp-server suite), package:lint — all green.

Before un-parking, whenever that happens

• Rebase onto current master and re-run the full suite; regenerate auth-schema.ts + drizzle/ (pnpm -F @1c-odata/mcp-server auth:schema) if better-auth moved in the meantime.
• De-duplicate changelog entries: this revert restores the @1c-odata/mcp patch notes embedded in mcp-server-admin-panel.md / mcp-server-multi-tenancy.md, while master carries the same content in .changeset/mcp-internal-reexports.md (or already released, in packages/mcp/CHANGELOG.md). Keep exactly one copy.
• ci.yml conflict with ci: bring back a published-package smoke for the surviving packages #166: master now carries a generic package-smoke job + .ci/package-smoke.sh (added after this branch was cut) covering the four library/stdio packages incl. @1c-odata/cli; this revert re-adds mcp-server's own deploy-package-smoke next to it. Keep both — they own different paths (tarball/exports/bin smoke vs the mcp-server auth/migrations boot) — and consider extending .ci/package-smoke.sh with a fifth isolated scratch for @1c-odata/mcp-server instead of resurrecting the overlap.
• Dependabot's docker/docker-compose entries come back with the deploy tree — check base-image currency (node, postgres, caddy) after a long park.