feat(mcp): add `loopover-mcp tools search <query>` for fuzzy discovery across the ~150-tool combined surface

[JSONbored]

Context

Part of #6226 (MCP platform epic). Between packages/loopover-mcp's 42 locally-registered tools and src/mcp/server.ts's larger remote set, an agent or human user has no way to find the right tool other than reading the full loopover-mcp tools/tools --json listing top to bottom, or already knowing the exact name. Confirmed via this session's audit: no search/filter capability exists today.

Requirements

• Add loopover-mcp tools search <query> (and --json output), fuzzy-matching against each registered tool's name AND description (not name-only — a query like "stake" should surface get_subnet_stake_quote even if "stake" isn't in the tool's short name).
• Reuse whatever fuzzy-matching approach this CLI already uses elsewhere (check suggestCommand's typo-suggester in bin/loopover-mcp.js for an existing utility before adding a new dependency).
• Keep this local-CLI-only for now — the remote server's tool list is a separate concern; if this proves useful, a follow-up issue can consider exposing equivalent search via the remote server's own protocol surface.

Test Coverage Requirements

Match this package's existing test conventions; tests covering a query that matches by name, a query that matches by description only, and a query with no matches.

Deliverables

• loopover-mcp tools search <query> implemented, with --json support.
• Tests for name-match, description-match, and no-match cases.

Expected Outcome

A user or agent can find the right tool among ~150 without reading the entire list or already knowing its exact name.

Links & Resources

• Epic: MCP platform — shared-core decision + usage telemetry #6226 (parent epic)
• packages/loopover-mcp/bin/loopover-mcp.js (existing tools/tools --json command and suggestCommand's fuzzy-match utility, if one exists, to reuse)

[linear-code]

JSO-4398