fix(playwright): split saved-query nav+API into two waits for CI stability

The saved-query test waited for a single GET response with a 15 s budget
that had to cover full-page navigation, JS hydration, AND the API call.
Under CI load (parallel test suites) navigation alone exceeded 10 s,
leaving too little headroom for the API response.

Split into two sequential waits — PAGE_LOAD (10 s) for navigation, then
API_RESPONSE (15 s) for the hydration fetch — so each phase gets its own
timeout budget.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: sadpandajoe

superset-frontend/playwright/tests/sqllab/sqllab.spec.ts

@@ -232,14 +232,18 @@ test('saves a query and loads it from saved queries', async ({
   const queryLink = page.getByRole('link', { name: savedQueryTitle });
   await queryLink.waitFor({ state: 'visible', timeout: TIMEOUT.API_RESPONSE });
 
-  // Click the query name to open it in SQL Lab (exercises the list → SQL Lab path)
-  const savedQueryHydration = waitForGet(
-    page,
-    `api/v1/saved_query/${savedQueryId}`,
-    { timeout: TIMEOUT.API_RESPONSE },
-  );
+  // Click the query name to open it in SQL Lab (exercises the list → SQL Lab path).
+  // Split into two waits so each phase gets its own timeout budget:
+  // 1. Full-page navigation (slow under CI load)
+  // 2. Saved-query API hydration (fires in useEffect after paint)
   await queryLink.click();
-  await savedQueryHydration;
+  await page.waitForURL(/sqllab/, {
+    waitUntil: 'load',
+    timeout: TIMEOUT.PAGE_LOAD,
+  });
+  await waitForGet(page, `api/v1/saved_query/${savedQueryId}`, {
+    timeout: TIMEOUT.API_RESPONSE,
+  });
   await sqlLabPage.waitForPageLoad();
   await sqlLabPage.ensureEditorReady();