test(e2e): reorder assert-signed-in checks (Sign Out first)

Move 'Sign Out' to the lead assertion at 20s timeout. It's the same
shape (TouchableOpacity > Text) that Android already passes against,
so if it fails we know we're not actually signed in; if Sign Out passes
but Manage Profile still times out, we have a specific iOS accessibility
quirk to chase rather than a generic timing issue.

Diagnostic-only reorder — same three assertions, different order.

Author: chriscanin

integration/mobile/flows/common/assert-signed-in.yaml

@@ -7,12 +7,17 @@ appId: com.clerk.clerkexpoquickstart
 # Screenshot the state we landed in BEFORE the assertion so a future
 # failure here has something to look at instead of just "timed out".
 - takeScreenshot: debug-assert-signed-in-state
-- extendedWaitUntil:
-    visible: "Manage Profile"
-    timeout: 20000
+# Check "Sign Out" first — it's the most reliable signal that we're on
+# the signed-in landing screen, and the same assertion shape that Android
+# already passes against. If this fails we genuinely aren't signed in;
+# if THIS passes but "Manage Profile" below fails, we have an iOS-specific
+# accessibility issue with the TouchableOpacity wrapping the text.
 - extendedWaitUntil:
     visible: "Sign Out"
-    timeout: 5000
+    timeout: 20000
 - extendedWaitUntil:
     visible: "Welcome"
     timeout: 5000
+- extendedWaitUntil:
+    visible: "Manage Profile"
+    timeout: 10000