muster release v5.30.0

Spans name the backend of a tool call. A call through call_tool set mcp.tool.name=call_tool on muster’s spans and no tool name on the client span to the backend, so a trace could not be filtered by backend tool or server. The client span to the backend now carries gen_ai.tool.name (the backend-native tool name, from the OpenTelemetry GenAI semantic conventions for MCP) and mcpserver.name; the inbound mcp.tools/call server span and the tool.<tool> span carry mcpserver.name and muster.downstream.tool.name (the exposed name, as in muster_downstream_tool_calls{tool}), and mcp.tool.name still names the invoked tool. A workflow.step span is labelled by its own dispatch; the workflow’s server span is not. (giantswarm/giantswarm#36711)