ci(mobile-e2e): bump iOS timeout 60->90min for cold-cache runs

Cancelled run 26253322728 showed every flow passing in order, but the
job hit its 60-minute wall at the 22-minute install/build mark plus
~5-8 minutes per top-level flow on iOS sim. iOS is inherently slower
than Android (ASWebAuthenticationSession setup, simctl install per
launch, SwiftUI a11y-tree population) — the suite just runs out the
clock on cache-miss days.

Bumping the wall to 90 to clear that comfortably. Drop back down once
we shard or persist DerivedData across runs.

Author: chriscanin

.github/workflows/mobile-e2e.yml

@@ -602,7 +602,15 @@ jobs:
     # our trial (capacity / label availability) — revisit when Blacksmith
     # exposes a label we know is provisioned on this account.
     runs-on: macos-15
-    timeout-minutes: 60
+    # 90 minutes accounts for: ~10 min monorepo install, ~12 min iOS build +
+    # SPM checkout on a cold derived-data cache, ~3 min cold-sim warmup,
+    # then ~5-8 min per top-level flow on iOS sim (vs ~45s on Android — iOS
+    # ASWebAuthenticationSession + simctl install are inherently heavier).
+    # The previous 60 was tight enough that the suite was killed mid-run on
+    # cache-miss days even with every flow passing. Tighten this back down
+    # once we either (a) parallelize flows across shards or (b) move iOS to
+    # a runner with persistent DerivedData caching.
+    timeout-minutes: 90
     steps:
       - name: Checkout @clerk/javascript
         uses: actions/checkout@v4