Android: NativeUserLocation without "mode" keeps the map rendering every frame (native default is COMPASS)

What happens

A completely static map with a plain <NativeUserLocation /> keeps MapLibre's
render thread pinned at ~100% of a core, forever. Nothing on screen moves, JS is
fully idle (React profiler shows zero commits), the map is just quietly cooking
a CPU core in the background. Lowkey a battery killer on real devices, since the
loop runs the whole time the map is visible. iOS is not affected.

Repro

1. Render a MapView with <NativeUserLocation /> and no mode prop on Android
2. Grant location permission
3. Run adb shell top -H -p <app pid> and watch a RenderThread N thread sit at ~100%

Reproducible with the library's own UserLocation example, nothing app-specific
needed.

Why

The docs say mode defaults to "default", but the @ReactProp setter only
runs when the prop is actually passed, so the view's internal default wins, and
that is RenderMode.COMPASS:
https://github.com/maplibre/maplibre-react-native/blob/2921af64b2c6/package/android/src/main/java/org/maplibre/reactnative/components/location/MLRNNativeUserLocation.kt#L24

COMPASS subscribes to the compass sensor, and every sensor tick re-animates the
puck bearing, so the map never stops drawing (it even burns with no location fix
and no visible puck). On iOS the codegen default is Default, so the two
platforms currently ship different defaults for the same prop.

Workaround

Pass mode="default" explicitly. Render thread drops to 0% on a static map.

Suggested fix

Flip the internal Android default to RenderMode.NORMAL so it matches the docs
and iOS.

Environment

@maplibre/maplibre-react-native 11.3.6 (also present on current main),
RN new architecture (bridgeless), Expo SDK 57, Android emulator API 35.

Start in package/android/src/main/java/org/maplibre/reactnative/components/location/MLRNNativeUserLocation.kt at the internal render-mode default, then reproduce the UserLocation example and observe RenderThread with adb shell top. Done means an unconfigured NativeUserLocation uses the documented default on Android and a static map no longer continuously renders or pins a core.