Fix streamable HTTP timeout handling

[nancyjlau]

upgrade hud.environment.connectors.mcp_config to keep sse_read_timeout only for SSETransport and avoid passing the deprecated timeout arg to StreamableHttpTransport and preserve the effective timeout for streamable HTTP by routing it through the client/session timeout path instead

---

Note

Medium Risk
Changes how remote transport timeouts are applied for streamable HTTP by passing them via the FastMCP client/session instead of transport construction, which could alter connection behavior for remote MCP servers if misconfigured.

Overview
Fixes timeout handling for remote MCP connections by only setting sse_read_timeout on SSETransport and avoiding deprecated timeout-style args for StreamableHttpTransport.

For streamable HTTP, the effective timeout is now stored on the transport (_hud_client_timeout) and forwarded by Connector.connect() as the FastMCP client timeout kwarg; tests were added/updated to lock in this behavior for both transport types.

^{Written by Cursor Bugbot for commit 91296c3. This will update automatically on new commits. Configure here.}