build(deps): update dependencies across android-maps-utils

[dkhawk]

Automated dependency updates for android-maps-utils on single persistent branch deps/auto-update.

All 39 unit tests and Gradle build verification tasks passed cleanly (./gradlew testDebugUnitTest --continue).

[googlemaps-bot]

Code Coverage

Overall Project	41.2% -0.02%	🍏
Files changed	86.67%	🍏

File	Coverage
HeatmapTileProvider.kt	81.19% -0.25%	🍏

[dkhawk]

Note on Dependency Version Caps (core-ktx & lifecycle-viewmodel-ktx):

androidx.core:core-ktx is capped at 1.18.0 (and androidx.lifecycle:lifecycle-viewmodel-ktx at 2.10.0), despite newer releases (1.19.0 and 2.11.0) being published on Google Maven.

• Reason: 1.19.0 and 2.11.0 strictly require Android API 37 (compileSdk = 37) and Android Gradle Plugin 9.1.0+. Adopting them directly on compileSdk = 36 / AGP 8.13.2 fails AAR metadata check verification:

  Dependency 'androidx.core:core-ktx:1.19.0' requires libraries and applications that depend on it to compile against version 37 or later of the Android APIs.
  :library is currently compiled against android-36.
  

• Lint False Positives: If Android Studio or [GradleDependency] checks report that 1.19.0 or 2.11.0 is available, note that this is a numerical check against repository indices that does not check transitive compileSdk cutoffs. 1.18.0 and 2.10.0 are the maximum valid stable releases for our current compileSdk 36 baseline.

[kikoso]

Do we want to update to the latest dependency version, @dkhawk ?

Also, since we will be merging the refactor PR, I wonder if it could make sense to make sure that the rewrite branch is updated, instead of main, which will be temporary.

[LoyalAbbas]

Since we're already rewriting the code, could we migrate directly to compileSdk = 37? Also, instead of merging this into main, would it make sense to merge it into the rewrite branch for now? Once all the code is updated, we can merge everything into main together.