Apply check-for-equals-in-render-object-setters & consistent-update-render-object to popular packages on pub.dev automatically

[fzyzcjy]

We all know that, the code quality of (popular) packages on pub.dev usually will not be higher than the Flutter framework itself. Therefore, given that the two linter rules have found out about 7 issues in the flutter framework itself, I guess it will also find out many for (popular) packages on pub.dev.

Thus, I suggest that, we may download the (popular) packages on pub.dev, and scan them just like scanning flutter framework. Then, we can even use GitHub's API (the gh command line, or the restful api, etc) to automatically raise issues onto the github issue tracker for those packages.

As for the details: To avoid scanning too many, we may simply scan the most popular packages (https://pub.dev/packages?sort=popularity), or the 67 flutter-favorite packages (https://pub.dev/packages?q=is%3Aflutter-favorite) etc. We may also make the linter has less false positives to avoid labor work of checking every result.

[incendial]

Oh, automating such process would be a great thing, actually!