[google_maps_flutter_web] Move integration tests to example. (flutter…

…#3675)

This PR moves the integration tests of this package to conform with the latest best practices for web plugins.

[webview_flutter] Run CocoaPods iOS tests in RunnerUITests target (fl…

…utter#3664)

[path_provider] Make a 0.0.5 for Dart 2.12 compat (flutter#3672)

Anything with a transitive dependency on `path_provider` (which is a
lot) is broken on Flutter 1.26 due to Dart FFI changes. path_provider
2.0.0 doesn't have this problem, but for transitive dependencies that
means users need to force an override in their pubspec (and more
importantly, know that they need to do so).

This creates a new minor release to path_provider_windows that uses a
1.26-friendly version of FFI, but has the null safety changes and major
version bump backed out, so that transitive dependencies can safely
resolve to this working version just by doing a pub update.

[image_picker] Run CocoaPods iOS tests in RunnerUITests target (flutt…

…er#3663)

[google_maps_flutter_web] Make google_maps_flutter_web work with late…

…st plugins (flutter#3673)

Co-authored-by: David Iglesias Teixeira <ditman@gmail.com>

[in_app_purchase] fix plugin version (flutter#3654)

[connectivity_for_web] Migration to null-safety. (flutter#3652)

[connectivity_for_web] Migration to null-safety. (flutter#3652)

Update plugin_platform_interface min version (flutter#3650)

To avoid intra-repo plugin conflicts during the NNBD stable migration,
`plugin_platform_interface` allowed either 1.x or 2.0. However, 1.0.x
isn't null-safe so this can cause apps that don't have all their
packages fully updated can fail to run in strong mode (due to having an
old local `plugin_platform_interface`.

Now that everything has been updated, we can bump all the minimums so
that people updating their plugins will get new versions of the
dependency.

Update plugin_platform_interface min version (flutter#3650)

To avoid intra-repo plugin conflicts during the NNBD stable migration,
`plugin_platform_interface` allowed either 1.x or 2.0. However, 1.0.x
isn't null-safe so this can cause apps that don't have all their
packages fully updated can fail to run in strong mode (due to having an
old local `plugin_platform_interface`.

Now that everything has been updated, we can bump all the minimums so
that people updating their plugins will get new versions of the
dependency.