MCP tool rename

[JSONbored]

Problem: Roughly three dozen tool names in the local MCP package are prefixed with the old brand name and are directly visible to any MCP client (and to any saved prompt or agent config referencing them by exact string).

Area: MCP package

Proposal: Introduce equivalents under the new prefix as the primary names. Keep the old names as thin, working aliases — same behavior, marked deprecated in their description — for one full minor-version deprecation cycle before removal.

Deliverables:

• New tool names shipped for the full existing tool surface.
• Matching deprecated aliases shipped alongside them.

Acceptance criteria:

• Calling a tool by either its old or new name produces identical behavior during the deprecation window.
• The deprecation notice is visible in the aliased tool's description.

Test scenarios:

• Call a representative sample of tools by both old and new names and diff the results.

Resources:

• The MCP package's tool-definition file and its server identifier.

Boundaries:

• Do not remove the old tool names in this PR — that happens in the cleanup step, after the deprecation window elapses.

---

Part of #4761.

[linear-code]

JSO-3447