[google_maps_flutter] Replace FGM_USING_COCOAPODS with the built-in COCOAPODS

[stuartmorgan-g]

Rather than setting our own define to detect CocoaPods-based builds, use the built-in COCOAPODS define.

May address flutter/flutter#183441

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.

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. ↩ ↩²

[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: code refactor with no semantic change

[gemini-code-assist]

Code Review

This pull request replaces the custom FGM_USING_COCOAPODS preprocessor macro with the standard COCOAPODS macro to detect CocoaPods-based builds. The change involves removing the custom macro definition from the .podspec files and updating the conditional import logic in several GoogleMapsUtilsTrampoline.h header files across different versions of the google_maps_flutter_ios plugin.

[vashworth]

@stuartmorgan-g Can you verify that this does not break a normal Flutter app that's using both SwiftPM and CocoaPods? I think COCOAPODS=1 may get passed to the Runner target and therefore also maybe the google_maps_sdk* plugin since it's static

[stuartmorgan-g]

You're correct, it's set for Runner (via the included xcconfig), and breaks the build. Good catch.

So much for this approach then :(