Demo: force an Android Release E2E failure to exercise CI retries (#59571)

Summary:

Demo only, stacked on the retry-chain fix so the exported PR shows the new behavior on real CI. Do not land.

This adds an RNTester Maestro flow that always fails, scoped so that only the Android Release E2E job runs it:
- `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.

The file name sorts it last, so every other flow still runs first.

What the PR run should show:
- `test_e2e_android_rntester`: `test (debug)` passes and `test (release)` fails. Both checks are green (a soft failure in the step), and `retry_1` starts even if the passing Debug job finishes last.
- `test_e2e_android_rntester_retry_1` behaves the same way, and `retry_2` starts.
- `test_e2e_android_rntester_retry_2 / test (release)` is red on the "Run E2E Tests" step. It is the only red check from this chain, and there is no separate `report` job.
- "Re-run failed jobs" re-runs `retry_2 / test (release)`, which runs Maestro again and fails again.

Changelog: [Internal]

Differential Revision: D128044163

Author: GijsWeterings

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

@@ -0,0 +1,16 @@
+# DO NOT LAND. Fails on purpose in the Android Release E2E job only, to
+# exercise the CI retry chain.
+# - android-release-only: the Debug job excludes it.
+# - 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
+  - local-screenshot-baseline
+---
+- runFlow:
+    when:
+      platform: Android
+    commands:
+      - launchApp
+      - assertVisible: 'Deliberate failure to exercise the CI retry chain'