[image_picker_android] bump dependency version of package:image_picker_platform_interface

[CicadaCinema]

The usage

plugins/packages/image_picker/image_picker_android/lib/image_picker_android.dart

Line 174 in 95a1f2c

ImagePickerOptions options = const ImagePickerOptions(),

of the ImagePickerOptions class stipulates at least v2.5.0 of package:image_picker_platform_interface

• see c13e8a5#diff-22398a12b080f477ab1716a09c1e91ac492cd2255f5f7dc335033da535c02dfaR8 where ImagePickerOptions was introduced
• also see https://github.com/flutter/plugins/blob/main/packages/image_picker/image_picker_platform_interface/CHANGELOG.md#250

Pre-launch Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• I read the Tree Hygiene wiki page, which explains my responsibilities.
• I read and followed the relevant style guides and ran the auto-formatter. (Unlike the flutter/flutter repo, the flutter/plugins repo does use dart format.)
• I signed the CLA.
• The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
• I listed at least one issue that this PR fixes in the description above.
• I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy, or this PR is exempt from version changes.
• I updated CHANGELOG.md to add a description of the change, following repository CHANGELOG style.
• I updated/added relevant documentation (doc comments with ///).
• this PR is test-exempt.
• All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

[stuartmorgan-g]

Thanks for the submission! I filed flutter/flutter#108992 which I'll try to get to shortly, which would give us testing that would catch these kinds of issues. I'll come back to this once that's in place, since it would give this test coverage (which isn't strictly necessary here, but would be good).

[stuartmorgan-g]

Closing as obsoleted by #6207 (I forgot I would need to fix the violations in the PR that added the testing).

Thanks again for highlighting the systemic issue here!