fix(console): count the /i18n reads in the settle signal, as the data adapter's own fetch does (objectui#12034)

The adapter's request path is withSettleSignal(createAuthenticatedFetch()); the
two /i18n reads now take the whole of it, so an automated driver's idle
predicate waits for the application's translations too.

Claude-Session: https://claude.ai/code/session_01MgfduSkFrfM3eorB3UGfAU
Co-authored-by: Claude <noreply@anthropic.com>

Author: claude

.changeset/12034-console-i18n-after-signin.md

@@ -7,6 +7,6 @@ The console's sign-in page no longer reads `/api/v1/i18n`, and the application's
 The two loaders the console hands to `I18nProvider` used to run as soon as the page loaded, before the session was known, with a bare `fetch`. So the sign-in page read `/api/v1/i18n/translations/:locale` and `/api/v1/i18n/locales` as an anonymous caller, and a signed-in page load sent no bearer with them. Where no session cookie rides along (a console built with an absolute `VITE_SERVER_URL`), a framework that refuses an anonymous `/i18n` read (objectstack-ai/objectstack#22432) answers both with 401, and a signed-in user's application labels stay in the language they were authored in.
 
 - **Signed out:** neither loader sends a request. The sign-in page renders from the built-in language packs.
-- **Signed in:** both loaders wait for the console's `AuthProvider` to answer for the page load, then read through `createAuthenticatedFetch()`, the request path the data adapter uses (bearer, `X-Tenant-ID`, `Accept-Language`). Every console sign-in ends in a full-page navigation, so the page load after sign-in is the one that reads them.
+- **Signed in:** both loaders wait for the console's `AuthProvider` to answer for the page load, then read through `withSettleSignal(createAuthenticatedFetch())`, the request path the data adapter uses (bearer, `X-Tenant-ID`, `Accept-Language`, and the in-flight count `window.__objectui` reports). Every console sign-in ends in a full-page navigation, so the page load after sign-in is the one that reads them.
 
 Nothing published changes: no export, prop or language-pack key is added, and `I18nProvider` is used through its existing `loadLanguage` and `loadLocales` props.

apps/console/src/i18nSession.ts

@@ -19,9 +19,10 @@
  *
  * - Signed out: no request. The sign-in page renders from the built-in
  *   language packs alone.
- * - Signed in: the read goes through `createAuthenticatedFetch()`, the request
- *   path the data adapter uses for every signed-in read (bearer, `X-Tenant-ID`,
- *   `Accept-Language`, session-rotation adoption).
+ * - Signed in: the read goes through `withSettleSignal(createAuthenticatedFetch())`,
+ *   the request path the data adapter uses for every signed-in read (bearer,
+ *   `X-Tenant-ID`, `Accept-Language`, session-rotation adoption, and the
+ *   in-flight count an automated driver waits on).
  * - Not answered yet (the provider's `isLoading`): the loader waits. The wait
  *   ends when the session read does, and it never rejects.
  *
@@ -34,6 +35,7 @@
  * navigation, would keep the built-in packs until the next page load.
  */
 import { createAuthenticatedFetch, type AuthState } from '@object-ui/auth';
+import { withSettleSignal } from '@object-ui/app-shell';
 
 /** `null` while the session is unanswered: before the first read, and while it re-resolves. */
 let signedIn: boolean | null = null;
@@ -64,5 +66,5 @@ export function whenSessionAnswered(): Promise<boolean> {
   });
 }
 
-/** The data adapter's own authenticated request path, for the two `/i18n` reads. */
-export const i18nFetch = createAuthenticatedFetch();
+/** The data adapter's own request path (`AdapterProvider`), for the two `/i18n` reads. */
+export const i18nFetch = withSettleSignal(createAuthenticatedFetch());