MCP manifest validation now flags unknown tool names, with fuzzy-match suggestions and dedicated telemetry

What

• Publishing an artifact page whose manifest declares a connector but lists tool names that connector doesn't actually expose now produces a specific unknown_tools rejection, explaining that tools must be the connector's own top-level tool names (with a hint about MCP-gateway-style connectors).
• The manifest-capability validator cross-checks each connector's declared tools against its real top-level tool names, auto-corrects near-matches (case/underscore variants), and for anything still unmatched emits the new unknown_tools malformed-entry kind or a warning listing the connector, the unknown names, and the tools that do exist.
• The artifact_publish telemetry event's malformed_count is now net of a new unknown_tools_count bucket, tracked alongside opaque_id_count and host_unavailable_count.

Why Previously a manifest with a misspelled or nonexistent tool name would likely fail in a less specific or less helpful way. Now the error names the actual problem, suggests likely fixes for near-misses, and is tracked separately in telemetry so this failure mode is easier to diagnose.