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

[4rthurmonteiro]

Platform web 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 on the web. The implementation appears correct, and the core logic in convert.dart properly translates the new MapConfiguration options. I have provided one comment on the integration tests to address duplicated test names and code, suggesting a refactoring to improve clarity and maintainability.

[stuartmorgan-g]

There needs to be a return outside of this, to handle the case of an enum value being added, since it comes from a different package. See

packages/packages/google_maps_flutter/google_maps_flutter_web/lib/src/convert.dart

Lines 138 to 144 in 4d26fb7

	// The enum comes from a different package, which could get a new value at
	// any time, so provide a fallback that ensures this won't break when used
	// with a version that contains new values. This is deliberately outside
	// the switch rather than a `default` so that the linter will flag the
	// switch as needing an update.
	// ignore: dead_code
	return gmaps.MapTypeId.ROADMAP;

for an example.

In this case I would suggest making the function return a nullable value so the fallback can be null, and then at the call site checking that this returns a non-null value before setting the value in the options class.

[4rthurmonteiro]

Good point! Done.

[stuartmorgan-g]

Looks like the MapOptions fields this PR is using were added in 8.1.0, which is why downgraded analysis is failing.

[4rthurmonteiro]

Thanks! done.

[harryterkelsen]

LGTM if Stuart's comments are addressed

[harryterkelsen]

LGTM

[4rthurmonteiro]

hey @stuartmorgan-g I updated the PR with your points.