Correct Android onTapToFocus gesture and event delivery

[SproutSeeds]

Summary

I found two Android callback problems while testing your work in Tesla #814, which adds the callback requested in #590. Lifting the last finger after a pinch emits onTapToFocus, and queued discrete taps can be combined into one callback.

This correction suppresses the new callback after multiple pointer input and makes TapToFocusEvent noncoalescing. It also clarifies the iOS focusMode requirement in the two API descriptions. The existing native focus and zoom paths retain their behavior. Four files, 13 additions and three deletions against your 36be2b6 head.

How did you test this change?

I compared the original, your PR and the corrected native builds. Your PR fails three subscribed pinch assertions in each Android renderer. Three valid Paper queue trials each accept four native window taps but deliver one callback. The correction passes those controls.

Final Paper and Fabric each pass 44 checks covering pinch, repeated taps, cancellation, callback removal/restoration, remounts, queued delivery and ten returns from Home. Android builds and TypeScript pass. The full iOS Paper bridge suite passes three methods and 13 preview tap cases. On my iPhone 15 Pro Max, I confirmed focus, pinch without tap callbacks, continued focus/zoom without the callback and restored delivery afterward.

Reproduction fixtures, results and exact commits, failure classifications.

Full iOS controls build with CLT clang 17. Default clang 21, Jest and explicit ESLint have matching baseline setup failures. Android optics are emulated; queue tests use bundled apps with developer support off. Earlier debug stress and emulator failures remain in the report. Physical Android optics and hosted execution are unverified; upstream workflows await approval with zero jobs.

Cody