fix: separate TimeoutError handling for better error reporting

Per Copilot AI review: distinguish timeout scenarios from actual
cleanup failures by catching TimeoutError separately. This helps
with debugging by providing clearer error messages.

Author: Sourabsb

core/framework/runner/mcp_client.py

@@ -436,6 +436,9 @@ def disconnect(self) -> None:
                     )
                     cleanup_future.result(timeout=5)  # Wait for cleanup with timeout
                     cleanup_attempted = True
+                except TimeoutError:
+                    # Cleanup took too long - may indicate stuck resources
+                    logger.warning("Async cleanup timed out after 5 seconds")
                 except Exception as e:
                     # This can happen if loop stopped between is_running() check and 
                     # run_coroutine_threadsafe(), or if cleanup itself failed