Fix Android headless test hangs

[brandonpage]

Summary

• replace the long-lived logcat stream with finite snapshots so a final SFTESTDONE line cannot remain buffered on Android 12L
• remove the invalid notification permission grant and disable SDK developer support in the headless test app, preventing the API 33+ permission-activity resume loop
• apply a 30-second timeout to each JavaScript test and an independent 30-second Android no-progress watchdog
• remove obsolete per-class timeout overrides and update the Android test documentation

Root cause

The test manifest intentionally removes POST_NOTIFICATIONS, but developer support is enabled by default for the debuggable test app. On API 33+, developer support requested the removed permission whenever the activity resumed. The permission controller immediately closed, resumed the app, and triggered another request. This repeatedly paused React Native and could prevent testCleanResyncGhosts, its JavaScript timeout, and SFTESTDONE from running.

The failing API 34 execution logged 502 permission requests. A previously passing API 34 execution logged 1,077 requests and had a 53.3-second result gap. After disabling developer support in the headless test app, every API 31–35 validation log had zero permission requests; the largest result gap was 2.96 seconds.

Validation

• :app:assembleDebug
• :app:assembleDebugAndroidTest
• git diff --check
• Firebase Test Lab, retries disabled:
  • API 31: 35/35 passed
  • API 32: 35/35 passed
  • API 33: 35/35 passed
  • API 34: 35/35 passed
  • API 35: 35/35 passed

[github-actions]

	Tests	Passed ✅	Skipped	Failed
iOS ^18 Test Results	36 ran	36 ✅

Test	Result
No test annotations available

• View iOS ^18 Test Results

[wmathurin]

Inline review feedback after checking the Workspace and ReactNative Android-test documentation.

[github-actions]

	Tests	Passed ✅	Skipped	Failed
iOS ^26 Test Results	36 ran	36 ✅

Test	Result
No test annotations available

• View iOS ^26 Test Results