Android Auto missing visibleArea & stableArea callbacks

Nobody has claimed this yet.

## Environment

- Android OS version:All with Android Auto Beta version 15.9.655104-release
- Devices affected: All with Android Auto Beta version 15.9.655104-release
- Maps SDK Version:11.14.0

## Observed behavior and steps to reproduce

VisibleArea & StableArea is not being triggered properly. Going from full screen to split screen theres no updates to these callbacks. Then going from split screen to the smallest screen theres an update to VisibleArea & StableArea but the Rect and EdgeInsets values are incorrect and it appears to always have full screen values.

This causes an issue where the navigation puck is not centered and looking out of place or not visible in all screen configurations except fullscreen

Also the actionstrips are permantly visible as well in full screen, they dont appear at all in split screen given the incorrect / not updated VisibleArea / StableArea

## Expected behavior

When switching between screen sizes in Android Auto there should always be 2 callbacks immediately, VisibleArea & StableArea triggered which should be followed by a VisibleArea call after roughly 10 seconds when actionstrips should be removed where possible

## Notes / preliminary analysis

Have noticed the same behaviour on other apps that use mapbox in Android Auto. I also tested Google Maps, Waze and Here we go (Here maps) and they all appear to still work as they should

## Additional links and references

We have a lot of Android Auto users so this is very concerning behaviour we see atm, and we do not know when Google plans to release these changes to the main production version of Android Auto

I also created a ticket with Google regarding this, but this does appear to be a mapbox only issue

No source file or test is named. Start by reproducing the Android Auto transitions between full, split, and smallest-screen modes with Maps SDK 11.14.0, then trace the VisibleArea and StableArea callback handling. Done means callbacks fire with correct Rect and EdgeInsets values, action strips behave as expected, and the navigation puck remains positioned across screen sizes.

Written by the indexing model from the issue text.