[in_app_purchase] Ensure purchases correctly report if they are ackno…

…wledged on Android (flutter#4257)

* Ensure purchases correctly show they are acknowledged

* Update packages/in_app_purchase/in_app_purchase_android/CHANGELOG.md

Co-authored-by: Rene Floor <[email protected]>

* Update packages/in_app_purchase/in_app_purchase_android/CHANGELOG.md

Co-authored-by: Rene Floor <[email protected]>

* Modify so public API is not changed

Co-authored-by: Rene Floor <[email protected]>

[camera] Fix a disposed camera controller throwing an exception when …

…being replaced in the preview widget. (flutter#4272)

[camera] Add Android & iOS implementations for pausing the camera pre…

…view (flutter#4258)

[camera] Replace device info with new device_info_plus (flutter#4265)

[camera] Expand CameraImage DTO with properties for lens aperture, ex…

…posure time and ISO. (flutter#4256)

[image_picker] Fix pickImage not returning on iOS when dismissing the…

… PHPicker view by swiping down. (flutter#4228)

[camera] android-rework part 9: Final implementation of camera class (f…

…lutter#4059)

This PR adds the final implementation for the Camera class that incorporates all the features from previous parts.

Fix and test for 'implements' pubspec entry (flutter#4242)

The federated plugin spec calls for implementation packages to include an `implements` entry in the `plugins` section of the `pubspec.yaml` indicating what app-facing package it implements. Most of the described behaviors of the `flutter` tool aren't implemented yet, and the pub.dev features have `default_plugin` as a backstop, so we haven't noticed that they are mostly missing (or in one case, incorrect).

To better future-proof the plugins, and to provide a better example to people looking at our plugins as examples of federation, this adds a CI check to make sure that we are correctly adding it, and fixes all of the missing/incorrect values it turned up.

Fixes flutter/flutter#88222

Fix and test for 'implements' pubspec entry (flutter#4242)

The federated plugin spec calls for implementation packages to include an `implements` entry in the `plugins` section of the `pubspec.yaml` indicating what app-facing package it implements. Most of the described behaviors of the `flutter` tool aren't implemented yet, and the pub.dev features have `default_plugin` as a backstop, so we haven't noticed that they are mostly missing (or in one case, incorrect).

To better future-proof the plugins, and to provide a better example to people looking at our plugins as examples of federation, this adds a CI check to make sure that we are correctly adding it, and fixes all of the missing/incorrect values it turned up.

Fixes flutter/flutter#88222

[shared_preferences] Fix possible clash of string with double entry (f…

…lutter#3895)