ci: Unpin Android E2E emulator once canary networking regression is fixed

[antonis]

Context

In #6378 we pinned the Android E2E emulator binary to build 15679343 (37.1.5.0) in .github/workflows/sample-application.yml (the Test android production REV2 job), via:

emulator-build: 15679343

This was a workaround for an unpinned canary emulator regression: channel: canary auto-updated the emulator to 37.1.6.0 (build 15726199), which broke emulator networking. Both the 10.0.2.2 host-loopback path to the mock Sentry server and external internet (the Spaceflight News fetch) lost egress, so the Spaceflight Maestro flow couldn't load articles and every envelope-waiting test timed out — 20/20 tests failed.

This was verified with a controlled experiment: same commit, same ubuntu-24.04 runner image, same aosp_atd;android-30 system image — only the emulator binary differed (37.1.5.0 green → 37.1.6.0 red). Re-pinning to 37.1.5.0 restored a fully green suite (20/20).

What to do

Once a fixed canary Android emulator ships (37.1.6.x+ with working networking), or once aosp_atd is available on a non-canary channel:

• Remove the emulator-build: 15679343 pin (and its comment) from the Test android production REV2 job in .github/workflows/sample-application.yml
• Optionally re-evaluate channel: canary / target: aosp_atd — switch to stable if ATD images become available there
• Confirm the Android E2E suite stays green on the latest emulator

References

• Pin PR: fix(ci): Pin Android E2E emulator to build 15679343 (37.1.5.0) #6378
• Affected job: Test android production REV2 in .github/workflows/sample-application.yml
• Upstream action: ReactiveCircus/android-emulator-runner

[linear-code]

RN-694