Run clang analyzer on iOS and macOS code in CI test when packages change

[jmagman]

Description

Add the --analyzer flag during linting to run clang analyzer.
Skip packages with known analyzer warnings.
I tested this by faking out a change in every package locally and confirmed this script still passes.

Related Issues

Fixes flutter/flutter#41443.

Checklist

Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

• I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
• My PR includes unit or integration tests for all changed/updated/fixed behaviors (See [Contributor Guide]).
• All existing and new tests are passing.
• I updated/added relevant documentation (doc comments with ///).
• The analyzer (flutter analyze) does not report any problems on my PR.
• I read and followed the [Flutter Style Guide].
• The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
• I updated pubspec.yaml with an appropriate new version according to the [pub versioning philosophy].
• I updated CHANGELOG.md to add a description of the change.
• I signed the [CLA].
• I am willing to follow-up on review comments in a timely manner.

Breaking Change

• Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
• No, this is not a breaking change.

[mklim]

LGTM

Skip packages with known analyzer warnings.

Some linters have a concept of a "baseline" instead, where you can save all existing errors and choose to ignore them but still fail if any new errors are introduced. I checked really quickly and that doesn't seem like it's possible with pod lib lint but I'm mentioning it because if it were I think it would be preferable to totally skipping the packages that fail already.

[mklim]

nit: Is there a bug tracking this?

[jmagman]

I created issues and updated the comment.

[jmagman]

LGTM

Skip packages with known analyzer warnings.

Some linters have a concept of a "baseline" instead, where you can save all existing errors and choose to ignore them but still fail if any new errors are introduced. I checked really quickly and that doesn't seem like it's possible with pod lib lint but I'm mentioning it because if it were I think it would be preferable to totally skipping the packages that fail already.

I figure analyzing most of the projects is better than analyzing none, though locking to a baseline would be nice!