fix(sdk): replace broken Accounts.loggingIn gate with sdk.account poll

The previous `Accounts.loggingIn?.()` gate threw at runtime
('Cannot read properties of undefined reading _loggingIn') because it
was called as a free reference and lost its `this` binding. The throw
was caught silently by runUserDataSync's try/catch, which meant the
gate never actually ran — boot timing happened to work because the
microtask between the throw and synchronizeUserData's stream subscribe
gave adopt enough time to populate sdk.account.

Replace it with an explicit ~500ms poll on sdk.account.uid. If the
Meteor-routed resume login (via stubMeteorStream → SDK socket → adopt)
completes within the window, we short-circuit and avoid issuing a
duplicate loginWithToken on the same socket — the duplicate causes a
second Presence connection, the aggregate stays online instead of
flipping to away, and the omnichannel idle/away tests fail. If adopt
doesn't fire in time, fall back to our own loginWithToken (existing
inflightLogin gate keeps it idempotent).

Verified: login, account-login, e2ee-key-reset and the full
omnichannel-rooms-forward suite pass locally.

Author: ggazzo

apps/meteor/client/lib/sdk/ddpSdk.ts

@@ -85,26 +85,18 @@ export const ensureConnectedAndAuthenticated = async (): Promise<void> => {
 		return;
 	}
 
-	// Wait for Meteor's own login (resume) flow to settle before issuing our
-	// own loginWithToken. Meteor's resume goes through Connection._send →
-	// stubMeteorStream → SDK socket and the response triggers
-	// adoptAccountFromMeteorLoginResult which sets sdk.account.uid. If we
-	// race ahead and call sdk.account.loginWithToken here, the SDK socket
-	// receives TWO `login` method frames; ddp-streamer's Account.login
-	// has no dedup, so each fires Accounts.onLogin → Presence.newConnection
-	// → a duplicate connection in usersSessions. The duplicate stays
-	// 'online' while the active one flips to 'away' on idle, and
-	// processConnectionStatus prefers ONLINE over AWAY in the aggregate —
-	// so auto-away never propagates and the navbar badge stays online.
-	const accountsLoggingIn = (Accounts as unknown as { loggingIn?: () => boolean }).loggingIn;
-	const start = Date.now();
-	while (accountsLoggingIn?.() && Date.now() - start < 2000) {
-		await new Promise<void>((resolve) => setTimeout(resolve, 50));
-		if (sdk.account.uid) return;
+	// Give Meteor's own login flow (resume routed through stubMeteorStream
+	// + adoptAccountFromMeteorLoginResult) time to populate sdk.account
+	// before we issue our own loginWithToken. If adopt fires first, we can
+	// short-circuit and avoid sending a second login frame on the SDK
+	// socket — which would otherwise create a duplicate Presence
+	// connection (processConnectionStatus prefers ONLINE over AWAY in the
+	// aggregate, breaking the auto-away flow). 500ms covers a single
+	// server roundtrip in CI; if the stub-routed login hasn't completed by
+	// then, fall back to issuing our own loginWithToken below.
+	for (let i = 0; i < 20 && !sdk.account.uid; i++) {
+		await new Promise<void>((resolve) => setTimeout(resolve, 25));
 	}
-	// One more microtask so the adopt callback (registered as ddp.onResult
-	// in the stub) has a chance to fire ahead of us.
-	await new Promise<void>((resolve) => setTimeout(resolve, 0));
 	if (sdk.account.uid) {
 		return;
 	}