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.

Author: stuartmorgan-g

packages/camera/analysis_options.yaml

@@ -0,0 +1 @@
+include: ../../../analysis_options_legacy.yaml

packages/camera/camera/analysis_options.yaml

@@ -0,0 +1 @@
+include: ../../../analysis_options_legacy.yaml

packages/camera/camera_platform_interface/analysis_options.yaml

@@ -0,0 +1 @@
+include: ../../../analysis_options_legacy.yaml

packages/camera/camera_web/analysis_options.yaml

@@ -22,9 +22,9 @@ dependencies:
  sdk: flutter
  flutter_web_plugins:
  sdk: flutter
+ pedantic: ^1.11.1
  stream_transform: ^2.0.0
 
 dev_dependencies:
  flutter_test:
  sdk: flutter
- pedantic: ^1.11.1

packages/camera/camera_web/pubspec.yaml

@@ -0,0 +1 @@
+include: ../../../analysis_options_legacy.yaml

packages/google_maps_flutter/analysis_options.yaml

@@ -0,0 +1 @@
+include: ../../../analysis_options_legacy.yaml

packages/google_maps_flutter/google_maps_flutter/analysis_options.yaml

@@ -0,0 +1 @@
+include: ../../../analysis_options_legacy.yaml

packages/google_maps_flutter/google_maps_flutter_platform_interface/analysis_options.yaml

@@ -24,13 +24,13 @@ dependencies:
  google_maps_flutter_platform_interface: ^2.1.2
  google_maps: ^5.2.0
  meta: ^1.3.0
+ pedantic: ^1.10.0
  sanitize_html: ^2.0.0
  stream_transform: ^2.0.0
 
 dev_dependencies:
  flutter_test:
  sdk: flutter
- pedantic: ^1.10.0
 
 # The example deliberately includes limited-use secrets.
 false_secrets: