chore(ci): bump seed-ws2 task budget to 45min for cold WS2 Livy starts

The orchestrator was killing the WS2 cross-workspace seed at the 25 min
wall-clock cap before the adapter's session-start retry loop could
complete. With session_start_timeout=600s and connect_retries=3, the
worst-case budget is ~4 × 600s = 2400s; bump TimeoutInMinutes 25 → 45
so the existing retry logic can ride out cold-start windows on WS2.
Healthy-Fabric runs (seed completes in ~5 min) are unchanged.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: mdrakiburrahman

tests/functional/test_config.yaml

@@ -45,7 +45,7 @@ tasks:
   - Command: uv run python -m tests.functional.orchestrator seed-ws2
     Name: Seed cross_ws_fixture into WS2 lakehouse
     Group: Provision-Infra
-    TimeoutInMinutes: 25
+    TimeoutInMinutes: 45
 
   - Command: uv run python -m tests.functional.orchestrator create-session --schema-mode no_schema --count 4
     Name: Create Livy session (no_schema)