This will be a stepping stone towards: #33440

Running the entire flutter/plugins test suite is too slow for it to be included as-is in flutter/tests. Though running just the analysis step should detect early:

• Dart build errors.
• New failing lints.
• Dependency resolution issues.

Work plan:

• Remove custom analysis_options and fix all result lint errors for in_app_purchase (done [in_app_purchase] Remove the custom analysis options, fix failing lints. plugins#3220).
• Remove custom analysis_options and fix all result lint errors for camera (in progress [camera] Add missing Dartdocs plugins#3229).
• Remove custom analysis_options and fix all result lint errors for video_player_web ([multiple] Remove custom analysis_options.yaml from web plugins. plugins#3238).
• Remove custom analysis_options and fix all result lint errors for url_launcher_web ([multiple] Remove custom analysis_options.yaml from web plugins. plugins#3238).
• Remove custom analysis_options and fix all result lint errors for google_maps_flutter_web ([multiple] Remove custom analysis_options.yaml from web plugins. plugins#3238).
• Add a flutter/flutter sharded test for executing the flutter/plugins analysis phase (Add a post-submit test shard for flutter/plugins tests #70887, Pin the version of flutter/plugins to test against #71166).
• Configure a Luci builder for running the new test shard.
• Set-up a process that promises regular updates for flutter/plugins version we're testing against.
• Make the new test a tree blocker.