fix: split HTTP connect/read timeouts (Jellyfin build + qBit stats)

Every HTTP client passed an integer timeout to requests, applying the same
value to BOTH connect and read phases. A slow Jellyfin /Items page or qBit
/sync/maindata blew through the 10s read budget → ReadTimeoutError. Split
into a (connect=5s, read=60s default) tuple via shared http_timeout() helper.
The media index build worker uses a 180s read floor. Existing services with
low timeout_seconds benefit from bumping to 60+.

backend/src/media_library_viewer_api/integrations/qbittorrent.py

@@ -35,7 +35,7 @@ def test_connection(
         base_url = str(config.get("base_url") or "")
         username = str(secrets.get("username") or "")
         password = str(secrets.get("password") or "")
-        timeout = int(config.get("timeout_seconds") or 10)
+        timeout = int(config.get("timeout_seconds") or 60)
         client = QbittorrentClient(base_url, username, password, timeout=timeout)
         data = client.maindata()
         version = str(data.get("server_state", {}).get("qbittorrent_version", "") or "connected")
@@ -53,7 +53,7 @@ class QbittorrentConfig(ServiceConfigBase):
     """Non-secret qBittorrent connection config."""
 
     base_url: ServiceBaseUrl
-    timeout_seconds: int = 10
+    timeout_seconds: int = 60
 
 
 class QbittorrentWidgetConfig(WidgetConfigBase):