[google_maps_flutter_platform_interface] Add cameraControl enable/disable & position on web

[4rthurmonteiro]

Platform interface portion of #9089.

Part of flutter/flutter#167137

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 adds support for enabling, disabling, and positioning the camera control button for the web version of Google Maps. This is achieved by adding webCameraControlEnabled and webCameraControlPosition to the MapConfiguration class, along with a new WebCameraControlPosition enum. The changes are consistently integrated throughout the MapConfiguration class, including updates to equality checks, hash code generation, and diffing logic. Corresponding tests have been added to verify the new functionality, and the package version and changelog have been updated. I have found one minor documentation error that should be corrected.

[stuartmorgan-g]

Nit: Needs a period at the end.

[4rthurmonteiro]

done.

[stuartmorgan-g]

Nit: Blank line above this; per Effective Dart style, there should be a blank line after the first sentence in a doc comment.

[4rthurmonteiro]

done.

[stuartmorgan-g]

Nit: please add a line break after the URL so this line isn't so long.

[4rthurmonteiro]

done.

[stuartmorgan-g]

Line break and blank line after the period.

[stuartmorgan-g]

This applies to all the comments below as well.

[4rthurmonteiro]

done.

[stuartmorgan-g]

LGTM

[harryterkelsen]

LGTM!

[4rthurmonteiro]

Hey @harryterkelsen @stuartmorgan-g,

I'm unable to merge this pull request, and I have a question about the next step.

I'm following the documentation for "Changing federated plugins" and am at step 4, which says: "Once it has been reviewed, landed, and published, update the initial PR..."

Who is responsible for landing and publishing the changes?

Thanks

[stuartmorgan-g]

The Flutter team (generally the last reviewer) lands changes, and a bot publishes them.

[4rthurmonteiro]

The Flutter team (generally the last reviewer) lands changes, and a bot publishes them.

thanks @stuartmorgan-g! Once the new version is published, I'll update the other pull request to reflect the changes.