There was some variation in pubspec.yaml formatting files in flutter/plugins, which was mildly annoying when making large changes or moving between plugins:

• section order (e.g., environment being on the bottom in some, and the top in others).
• sort order of dependencies.

There are also some best-practices that we should follow for our monorepos:

• use repository instead of homepage since it gives a better repo link (pub.dev guesses if it's not set), and we don't really have a meaningful "homepage" for the plugin other than that.
• use issue_tracker with a link to a label search, since otherwise it's not very useful.

I'm doing a bunch of manual cleanup on this now, but we should consider enforcing it in CI so we don't end up in the same place in several years. repository and issue_tracker in particular are likely worth enforcing since they affect the actual published package's pub.dev presentation.