fix(android): MarkerView touch/press on new architecture (Fabric)

[mfazekas]

Fixes #3832
Fixes #3934
Fixes #3440
Fixes #3981

Problem

On Android with the new React Native architecture (Fabric/TurboModules), any interactive content inside a MarkerView — buttons, sliders, switches, TextInput — silently failed. Touches appeared to land nowhere, onPress was never fired, and press feedback (opacity, scale) didn't show.

Root cause: Mapbox positions view annotations by calling setTranslationX/Y directly on the native view. This is a render-layer transform — it moves the view visually but does not update the view's Yoga layout position. Fabric's shadow tree only tracks layout position, so UIManager.measure() always returned (0, 0), making every hit-region wrong.

A second issue: the MapView's own gesture recogniser was intercepting MOVE events mid-sequence (after DOWN), sending CANCEL to child Pressables and suppressing onPress even in cases where the hit-test was correct.

iOS is unaffected — Mapbox iOS positions annotations via frame assignment, which Fabric reads correctly.

Fix

Android — RNMBXMarkerViewContent.kt

• Override setTranslationX/Y to intercept Mapbox's position updates and fire a topAnnotationPosition event to JS.
• Deduplicate events via lastReportedTx/Ty to prevent a feedback loop when Fabric re-applies the same transform prop back to setTranslationX/Y.
• Override dispatchTouchEvent to call requestDisallowInterceptTouchEvent(true), preventing the parent MapView pan/zoom gesture from stealing MOVE events and cancelling child touches.

Android — RNMBXMarkerViewContentManager.kt

• Switch base class to AbstractEventEmitter and register topAnnotationPosition → onAnnotationPosition.

Codegen spec — RNMBXMarkerViewContentNativeComponent.ts

• Add onAnnotationPosition as a DirectEventHandler so Fabric's bridge knows about it.

JS — MarkerView.tsx

• Refactor from class to function component.
• Receive onAnnotationPosition events and apply the translation as a React transform on RNMBXMarkerView, keeping the Fabric shadow tree in sync with Mapbox's actual on-screen position.
• PixelRatio.get() divide: Android translationX/Y is in device pixels; React transforms expect logical pixels.

Example — MarkerView.tsx

• Add an InteractiveMarkerContent marker with two sliders, a switch, a counter, a TextInput, and a Pressable button to exercise the full range of complex interactivity inside a MarkerView.

Test plan

• Open the Marker View example on Android (new arch)
• Tap the blue button inside the simple marker → onPress fires, blue flash visible
• Drag the Hue and Opacity sliders in the interactive marker → values update live
• Toggle the Switch → state flips
• Tap +/− counter buttons → counter increments/decrements
• Type in the Note field → keyboard appears, text updates
• Tap "Pressed N times" button → press count increments, button darkens on press
• Pan/zoom the map around the markers → map responds normally; markers stay interactive after re-positioning
• Verify iOS behaviour is unchanged