[google_maps_flutter_android] Add advanced markers support

[jokerttu]

This PR adds Advanced markers support to the Android implementation of google_maps_flutter.
Approved combined PR: #7882
Approved and merged platform interface PR: #9737
Issue: flutter/flutter#155526

Pre-Review Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• I read the Tree Hygiene page, which explains my responsibilities.
• I read and followed the relevant style guides and ran the auto-formatter.
• I signed the CLA.
• The title of the PR starts with the name of the package surrounded by square brackets, e.g. [shared_preferences]
• I linked to at least one issue that this PR fixes in the description above.
• I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy, or I have commented below to indicate which version change exemption this PR falls under¹.
• I updated CHANGELOG.md to add a description of the change, following repository CHANGELOG style, or I have commented below to indicate which CHANGELOG exemption this PR falls under¹.
• I updated/added any relevant documentation (doc comments with ///).
• I added new tests to check the change I am making, or I have commented below to indicate which test exemption this PR falls under¹.
• All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Note: The Flutter team is currently trialing the use of Gemini Code Assist for GitHub. Comments from the gemini-code-assist bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.

Footnotes

1. Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling. ↩ ↩² ↩³

[gemini-code-assist]

Code Review

This pull request introduces support for Advanced Markers in the Android implementation of google_maps_flutter. The changes are comprehensive, including dependency updates, new logic for handling AdvancedMarkerOptions like PinConfig and collisionBehavior, and the addition of AdvancedMarkerClusterRenderer for clustering. A new API, isAdvancedMarkersAvailable, is also included. The example app has been updated with new pages to demonstrate these features. The implementation is solid and well-tested. I have a couple of minor suggestions to improve code quality and maintainability.

[reidbaker]

Java code reviewed. Sorry this took so long but thank you so much for your contribution.

[jokerttu]

Hi, any update on this?

For context:

• reidbaker requested a review from camsim99 last month (in December)
• jokerttu requested a review from reidbaker last month (in December)

I just wanted to check whether anything is blocking a re-review. Please let me know if there’s anything else you need from me.

[camsim99]

Apologies for the delay. This looks good to me! We'll just need a second review to get this landed at this point.

[jokerttu]

Rebased and tested locally. Waiting second review.

[jokerttu]

@camsim99
Noticed that this commit has updated color handling for pigeon messaging.

Therefore I also updated new colors values for Advanced Markers to use the same mechanism on following commit: f45c208

[stuartmorgan-g]

From triage: @reidbaker did you want to review this again, or should it just be landed? We don't need a second review from a process standpoint since this is a team member PR.

[reidbaker]

I don't need a second pass but can give one of you think it will help

[stuartmorgan-g]

In that case @jokerttu please let us know if there's any area you would like additional review on, otherwise feel free to add the autosubmit label.

[auto-submit]

autosubmit label was removed for flutter/packages/10381, because - The status or check suite Windows_x64 repo_tools_tests has failed. Please fix the issues identified (or deflake) before re-applying this label.

• The status or check suite Linux repo_checks has failed. Please fix the issues identified (or deflake) before re-applying this label.

[stuartmorgan-g]

This failure is due to one of our repo tool dependencies publishing an update that broke an overly strict test; #11014 has the fix, and once that lands you'll need to merge in master again.