[Request]: Run flutter analyze workflow in proper scopes and enforce its results

[vbuberen]

Plugin

All

Use case

It makes no sense to run analyze on all packages in every PR.

Here is an example where in PR with device_info_plus files changes only I see warnings for another plugin, because the analyze task runs for all plugins:

Proposal

Suggest to do multiple changes:

• Run analyze only in the scope of changed files in PRs.
• Make analyzer warnings failing the set of CI checks to enforce issues resolutions, instead of catching up with fixes later as we do now.