agent-platform release v4.93.0

mcp-kubernetes.mcpServer: the bundled mcp-kubernetes registers as a member of muster’s kubernetes family, or not at all (giantswarm/agent-platform#403). With managementCluster: <name> the connectivity chart renders the MCPServer the way agent-platform-mcps renders every management cluster’s: <name>-mcp-kubernetes, labelled muster.giantswarm.io/management-cluster: <name>, with spec.family {name: kubernetes, instanceArg: management_cluster}. A single-installation deployment (the agentlab) gets the fleet’s x_kubernetes_<tool> tools, management_cluster: <name>-mcp-kubernetes selecting it (muster offers a family’s members by their MCPServer names). With enabled: false it renders no CR, and an agent-platform-mcps.mcpServers entry does the registration without a duplicate. The default, the family-less singleton mcp-kubernetes, is unchanged. The meta chart drops the block from the values forwarded to the mcp-kubernetes chart. make verify-mcp-kubernetes-registration.