feat(mapview): add compassEnabled prop for iOS and Android

[KirillKaverin]

Summary

Type of Change

• Bug fix
• New feature
• Breaking change
• Documentation update

Test Plan

Screenshots / Videos

Checklist

• I tested on iOS
• I tested on Android
• I tested on Web
• I updated the documentation (if needed)

Note

Behavior change: On iOS with provider="google", the compass button is now visible by default. If you want the previous behavior, set compassEnabled={false}.

[lodev09]

LGTM overall — implementation cleanly follows the existing pattern for boolean prop toggles (private field, equality short-circuit on Android, applyProps wiring on iOS, inclusion in applyUiSettings). Codegen + TS types + docs all consistent.

Two notes:

• Behavior change on iOS Google Maps. GMSMapView.settings.compassButton defaults to NO upstream; with compassEnabled defaulting to true, existing apps using the Google provider on iOS will start showing the compass button after upgrading. Likely intended (matches Apple/Android defaults), but worth calling out in the PR description / changelog.
• Web not updated. src/MapView.web.tsx doesn't handle the new prop. rotateEnabled has the same gap, so not a new regression — fine to defer.

Nit: PR body Summary / Test Plan are empty per the template in AGENTS.md.

[KirillKaverin]

@lodev09 the biggest problem that the rotate button shows only for 3D scenes in web (https://developers.google.com/maps/documentation/javascript/controls). I have tested in and the rotate button shows for 'satellite' and 'hybrid' maps. Also there is no gesture to rotate the map and show the real compass (rotate button is not the same as compass in iOS and Android)