test(e2e): handle post-password email-code verification step

After the --env fix, sign-in flow progresses through password entry
correctly but the instance routes to a "Check your email" verification
screen requiring a 6-digit code. The +clerk_test@ email pattern routes
mail to Clerk's test inbox and the verification code is the documented
constant "424242".

Add a conditional runFlow that enters 424242 if the verification screen
appears. Non-verification instances skip the block via the `when:
visible` guard.

Author: chriscanin

integration-mobile/flows/common/sign-in-email-password.yaml

@@ -25,6 +25,16 @@ appId: com.clerk.clerkexpoquickstart
     index: 0
 - waitForAnimationToEnd:
     timeout: 5000
+# Some instances require email-code verification AFTER a successful
+# password submit. For +clerk_test@ emails Clerk's documented test
+# verification code is "424242" — see https://clerk.com/docs/testing/test-emails-and-phones
+- runFlow:
+    when:
+      visible: "Check your email"
+    commands:
+      - inputText: "424242"
+      - waitForAnimationToEnd:
+          timeout: 5000
 # Android Google Password Manager may prompt to save the password after
 # sign-in. Dismiss it so assertions on the home screen work.
 - runFlow: