[robhogan]

RNTester ignores a deep link until its JS has rendered, but open-example.yml only waits for animations to end - which on a fresh iOS simulator happens ~1.4s after relaunch, before RNTester takes links at ~2.7s. Since #59994 sent the link once on iOS, 17 of 25 iOS capture jobs had a flow fail its first attempt this way (29 failures across almost every flow), and in one job the retries ran out.

This waits for the "Components" label in RNTester's tab bar, which is on every screen including a restored example, before linking once. That wait is optional, and as a backstop the helper now takes the ID of an element only the requested example has, then relaunches and links again until it's visible, up to 3 times. The five call sites that only waited for example-container now use a specific testID from their example.

Changelog: [Internal]

Test plan:
Ran every visual flow once (no Maestro retries) on a freshly erased iPhone 17 Pro simulator (iOS 27) with RNTester Release from CI. Locally the drop is deterministic:

Before the link	Result
main (wait for animations)	All 12 flows failed
retry with the animation wait	All 12 flows failed - every retry links too early
This PR	All 12 flows passed, twice, ~8 min each. The retry never fired, and the "Components" wait took 2.7s median, 3.1s max

maestro check-syntax passes for every flow.

On CI (run 43580332516), both platforms passed all 12 flows on their first attempt, with no relaunch retries and no "Components" timeouts. The iOS capture job took 19m, against 18-27m on main since #59994.