[google_maps_flutter] Removes unnecessary parentheses

[FMorschel]

This is solely a change to allow the CL for dart-lang/sdk#59069 to land.

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[^1].
• 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[^1].
• 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[^1].
• All existing and new tests are passing.

[flutter-dashboard]

It looks like this pull request may not have tests. Please make sure to add tests or get an explicit test exemption before merging.

If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix?

Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing.If you believe this PR qualifies for a test exemption, contact "@test-exemption-reviewer" in the #hackers channel in Discord (don't just cc them here, they won't see it!). The test exemption team is a small volunteer group, so all reviewers should feel empowered to ask for tests, without delegating that responsibility entirely to the test exemption group.

[stuartmorgan-g]

test-exempt: tested by analyzer change it unblocks

[stuartmorgan-g]

Please undo all of the unrelated formatting changes. It looks like you probably ran the formatter without running pub get first, and so it applied the wrong version of the formatter.

[FMorschel]

Fixed @stuartmorgan-g. Thanks!

[ditman]

The changes are so minimal, that I don't think this even needs a NEXT note in the changelog. @stuartmorgan-g ?

[stuartmorgan-g]

Yes, this is so clearly a no-op that we can exempt it from everything.

[ditman]

Restarted repo-checks and applied autosubmit label, this should land soon. Thanks @FMorschel!

[auto-submit]

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

[ditman]

@stuartmorgan-g it seems the script is not picking up the "no versioning needed" label?

Changed packages: google_maps_flutter_web
[0:00] Running for packages/google_maps_flutter/google_maps_flutter_web...
  No version change.
No version change found, but the change to this package could not be verified to be exempt
from version changes according to repository policy.
If this is a false positive, please comment in the PR to explain why the PR
is exempt, and add (or ask your reviewer to add) the "override: no versioning needed" label.

I'm going to click "Update branch" just in case it needs a fresh commit hash.

[stuartmorgan-g]

I'm going to click "Update branch" just in case it needs a fresh commit hash.

It's not supposed to, but Cocoon may have regressed again.