[ci] Exclude packages using deprecated APIs from the pod linter check

[jmagman]

Xcode 26 is showing deprecation usage as warnings: flutter/flutter#170437. These warnings are causing podspec-check to fail as these warnings are being treated as errors.
To unblock testing Xcode 26 in CI, exclude the existing exclude_xcode_deprecation packages from the podspec check command.

Currently used here:

packages/.ci/targets/ios_platform_tests.yaml

Line 21 in 83ae18a

args: ["xcode-analyze", "--ios", "--ios-min-version=14.0", "--exclude=script/configs/exclude_xcode_deprecation.yaml,script/configs/xcode_warnings_exceptions.yaml"]

packages/.ci/targets/macos_platform_tests.yaml

Line 18 in 83ae18a

args: ["xcode-analyze", "--macos", "--macos-min-version=14.0", "--exclude=script/configs/exclude_xcode_deprecation.yaml,script/configs/xcode_warnings_exceptions.yaml"]

This isn't a perfect solution, as the podspec check will find more issues than just deprecation warnings (Swift 6 warnings, for example), and this will prevent any warnings being discovered for these packages. However, I believe it's a better solution than #9428 (not treating warnings as errors for any package) because NEW regression warnings in all other packages can be caught in presubmit.

Closes #9428

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 aims to unblock CI on Xcode 26 by excluding packages with known deprecation warnings from the podspec-check. The change is well-reasoned and uses a separate configuration file for the exclusion list, which is good practice. My review includes one suggestion to improve the readability and robustness of the command-line arguments in the CI configuration file.

[stuartmorgan-g]

LGTM