Demo: fail an Android Release E2E flow on the first attempt only (#59573)

Summary:
Pull Request resolved: #59573

Demo only, stacked on the retry-chain fix so the exported PR shows on real CI that a failure which passes on retry still leaves CI green. Do not land.

This adds an RNTester Maestro flow that always fails, and makes `e2e-android-rntester.yml` exclude it (tag `demo-fail-first-attempt`) on retries (`retry-attempt > 0`). It behaves like a test that flakes once:
- `android-release-only` excludes it from the Android Debug job.
- `local-screenshot-baseline` keeps it out of the Maestro Cloud runs.
- A `when: platform: Android` condition makes it a no-op in the iOS E2E job.

It also tags `sectionlist-viewability.yml` `android-release-only`, because that flow currently fails in Android Debug on every attempt. Otherwise `retry_2 / test (debug)` would go red for an unrelated reason.

What the PR run should show:
- `test_e2e_android_rntester`: the Release "Run E2E Tests" step fails, but `test (release)` and `test (debug)` both finish green, and `retry_1` starts.
- `test_e2e_android_rntester_retry_1`: Release re-runs only the unfinished flows. The demo flow is excluded and the rest passed in the first attempt, so the job passes. Debug skips the run because every flow already passed.
- `test_e2e_android_rntester_retry_2` is skipped, and no check from this chain is red.

Changelog: [Internal]

Differential Revision: D128054792

Author: GijsWeterings

.github/workflows/e2e-android-rntester.yml

@@ -77,7 +77,7 @@ jobs:
           # These timing-sensitive flows remain covered by the release APK.
           # Running the debug ARM64 APK through native translation can delay
           # React commits long enough for Maestro to miss taps and assertions.
-          exclude-tags: ${{ matrix.flavor == 'debug' && 'android-release-only' || '' }}
+          exclude-tags: ${{ matrix.flavor == 'debug' && 'android-release-only' || (inputs.retry-attempt > 0 && 'demo-fail-first-attempt' || '') }}
       - name: Run E2E Tests
         # Same step without continue-on-error, so the final attempt fails
         # here. A step's continue-on-error expression doesn't see inputs.

packages/rn-tester/.maestro/sectionlist-viewability.yml

@@ -1,4 +1,7 @@
 appId: ${APP_ID} # iOS: com.meta.RNTester.localDevelopment | Android: com.facebook.react.uiapp
+# DO NOT LAND: skipped in Android Debug for the retry demo; it currently fails there.
+tags:
+  - android-release-only
 ---
 - launchApp
 - stopApp

packages/rn-tester/.maestro/zz-demo-retry-chain-flake.yml

@@ -0,0 +1,18 @@
+# DO NOT LAND. Fails on purpose in the first Android Release E2E attempt only,
+# to show that a failure that passes on retry keeps CI green.
+# - android-release-only: the Debug job excludes it.
+# - demo-fail-first-attempt: e2e-android-rntester.yml excludes it on retries.
+# - local-screenshot-baseline: keeps it out of the Maestro Cloud runs.
+# - The platform condition makes it a no-op in the iOS E2E job.
+appId: ${APP_ID}
+tags:
+  - android-release-only
+  - demo-fail-first-attempt
+  - local-screenshot-baseline
+---
+- runFlow:
+    when:
+      platform: Android
+    commands:
+      - launchApp
+      - assertVisible: 'Deliberate first-attempt failure to exercise the CI retry chain'