[google_maps_flutter_platform_interface] Adds support for mapTypeControlEnabled, fullscreenControlEnabled, and streetViewControlEnabled for web

[puneetkukreja98]

Part of #11955

Part of: flutter/flutter#104111

Context:
As suggested in the review - #11955 (review), this is a standalone sub-PR separating out just the platform interface changes.
It introduces the necessary configuration flags (mapTypeControlEnabled, fullscreenControlEnabled, and streetViewControlEnabled) to MapConfiguration to pave the way for the web implementation.

Pre-Review Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• I read the AI contribution guidelines and understand my responsibilities, or I am not using AI tools.
• 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 followed the version and CHANGELOG instructions, using semantic versioning and the repository CHANGELOG style, or I have commented below to indicate which documented exception 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 mapTypeControlEnabled, fullscreenControlEnabled, and streetViewControlEnabled properties to MapConfiguration in the google_maps_flutter_platform_interface package. The changes update the MapConfiguration class fields, constructor, diffing logic, equality operators, and hash code generation, and introduce corresponding unit tests. Since all review comments were filtered out because they focused on non-code version number changes, there is no additional feedback to provide.

[stuartmorgan-g]

In the future, please don't use the phrase "fixes some-issue-link" in sub-PRs. GitHub will auto-close issues when PRs land that say they fix an issue, and this PR does not, by itself, fix that issue, so should not result in the issue being closed.

[puneetkukreja98]

In the future, please don't use the phrase "fixes some-issue-link" in sub-PRs. GitHub will auto-close issues when PRs land that say they fix an issue, and this PR does not, by itself, fix that issue, so should not result in the issue being closed.

@stuartmorgan-g Understood, thanks for the guidance. I will avoid using the "fixes" keyword in the descriptions of sub-PRs going forward to prevent issues from auto-closing.