fix(e2e): Add scrolling to find crash control buttons in Android test

The crash control buttons are off-screen, so the Maestro flow needs to
scroll to find them before tapping. This matches the pattern used in
other Android E2E tests.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>

Author: antonis

samples/react-native/e2e/tests/captureAppStartCrash/captureAppStartCrash.test.android.manual.yml

@@ -5,7 +5,16 @@ appId: io.sentry.reactnative.sample
     clearState: true
     stopApp: true
 
-- tapOn: "Errors"
+# App launches on ErrorsTab by default, wait for screen to load
+- waitForAnimationToEnd:
+    timeout: 2000
+
+# Scroll down to find the "Enable Crash on Start" button (Android only)
+- scrollUntilVisible:
+    element: "Enable Crash on Start"
+    timeout: 10000
+    direction: DOWN
+
 - tapOn: "Enable Crash on Start"
 - stopApp
 
@@ -24,5 +33,14 @@ appId: io.sentry.reactnative.sample
     clearState: false
     stopApp: false
 
-- tapOn: "Errors"
+# Wait for app to stabilize
+- waitForAnimationToEnd:
+    timeout: 2000
+
+# Scroll down to find the "Disable Crash on Start" button
+- scrollUntilVisible:
+    element: "Disable Crash on Start"
+    timeout: 10000
+    direction: DOWN
+
 - tapOn: "Disable Crash on Start"