tree b3b6efdff7a384e285155c37a2cc939f11dfb327
parent 33968c0e9e223ca64dbd6e07dc4addf81cb7269f
author stuartmorgan <stuartmorgan@google.com> 1639087344 -0500
committer GitHub <noreply@github.com> 1639087344 -0800
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJhsnzwCRBK7hj4Ov3rIwAAUTwIAJPhNqY/U9VQLtWY6I/0K0gU
 l4d/17M79z3JsiyYDqweOJyU262ZMa6i/wj66p6CnseBIh4p1KF/Pv+xHwxYC9aJ
 AyjorW7Elj3mQ/epUQ0Z49IK5J87LF/mFa3X3xd7QCqE3WyewsUXGvnzMisHhfyV
 3nAk6Hp7+ufz00ARNeGN40vZGLPzdH2JN7qoY45d3q8s5XmR5b5rzYMq6Ll83cxU
 XMTDpH0zHSP0GdceOu8tBeloNvDD2POr6sFSam4cuACOTpTWz11PSG5CUthTDJpH
 ipAHtfQTtSvNQnOIn+acemaRxkQfBYnQzpYIliTjUanjT6kU2LeXSKw5lRBkUHk=
 =TJ9Y
 -----END PGP SIGNATURE-----
 

Move custom analysis options into sub-packages (#4603)

When the legacy analysis options were bulk-added to the repository to
allow transitioning incrementally to the Flutter analysis options, they
were added to top-level plugin groups. This makes it harder to migrate
incrementally, and also means that when we add a new sub-package (e.g, a
web or desktop implementation) it's automatically using the legacy
options.

This moves all the legacy option files into each individual package, and
updates the allow list for the tool accordingly, so that migration can
be done package by package.