feat(registry): publish axis to the official MCP registry

The npm listing was effectively invisible and untrustworthy: no keywords,
no repository link, no license, and a description ("Axis MCP Server CLI")
that told a reader nothing about what the thing does. npm search ranks on
description and keywords, so the package could not be found by anyone who
did not already know its name.

- package.json gains keywords, repository, homepage, bugs, author, and
  license (AGPL-3.0-only, matching the root LICENSE), plus a description
  that states the actual problem it solves.
- mcpName ties the npm artifact to the dev.useaxis/axis registry entry.
  The official registry requires this to prove the publisher controls the
  package, so it must ship inside the tarball, hence the version bump.
- README is the package page every developer lands on. It documented
  SUPABASE_SERVICE_ROLE_KEY and OPENAI_API_KEY, which is not how anyone
  connects; the real path is `claude mcp add` against the hosted board.
- server.json moves to the 2025-12-11 schema (camelCase registryType,
  explicit transport, repository id for rename/resurrection safety).

Verified against the published 1.14.0 artifact before claiming the entry:
the bin completes an MCP handshake over stdio, advertises 28 tools, and
keeps stdout clean JSON-RPC with the banner on stderr.