Release prep: agentcathq metadata, webmcp-server + extension 0.2.0, server publish job

[kashishhora]

What changed

Housekeeping needed before cutting the 1.1.0 release.

• package.json / packages/webmcp-server/package.json — repository, homepage, and bugs now point at agentcathq/webmcp-react. The repo was renamed; npm publish --provenance verifies repository.url against the repo the workflow runs in and rejects a mismatch, so publishing would fail as-is. Also dropped the stale navigator.modelContext keyword from the server package.
• webmcp-server → 0.2.0 — its bin picked up the CANCEL_TOOL forwarding in Extension + examples: migrate to document.modelContext, forward cancellation end to end #55.
• Bridge extension → 0.2.0 (manifest.json, extension/package.json) — it now runs on native Chrome ≥152 again and forwards cancellations.
• .github/workflows/publish.yml — a second publish-server job publishes packages/webmcp-server with provenance on the same release event, skipping if that version is already on npm (so library-only releases don't fail the job).
• CHANGELOG — the extension notes move from Unreleased into 1.1.0, since they ship on the same tag.

Test plan

• pnpm install --frozen-lockfile still clean; pnpm test passing (209)
• After merge: cut the v1.1.0 GitHub Release and watch both publish jobs. webmcp-server needs its own trusted-publisher entry on npmjs.com (agentcathq/webmcp-react, publish.yml) or its job will fail — the library's entry should be checked for the rename too.