Add proper elicitation support for ambiguous flow run names

[zzstoatzz]

Problem

When multiple flow runs have the same name, we want to prompt the user to select which one they want to inspect. Currently, the MCP client (Claude interface) doesn't support the elicitation feature, even though FastMCP provides it.

Current Workaround

The implementation currently returns an error message listing all matches with their UUIDs, requiring the user to:

1. See the error with all matches listed
2. Copy the desired UUID
3. Call the tool again with that specific UUID

Desired Behavior

When multiple flow runs match a name:

1. Tool prompts user interactively: "Which flow run would you like to inspect?"
2. User selects from the list
3. Tool returns the selected flow run details

All in a single interaction.

Technical Details

• FastMCP supports elicitation via ctx.elicit() method
• When we try to use it, we get "Method not found" error from the MCP client
• Implementation is ready in PR Add flow run name resolution with MCP elicitation #10 but commented out due to client limitations

Acceptance Criteria

• When MCP client supports elicitation, uncomment the elicitation code
• Single-step flow run selection for ambiguous names
• User gets prompted with clear options to choose from
• No need for manual UUID copying

Related

• PR Add flow run name resolution with MCP elicitation #10 has the initial implementation (with workaround)
• FastMCP elicitation docs: relevant section in FastMCP documentation