fix(all): Increase min Flutter version to fix dartPluginClass registration

[miquelbeltran]

Description

Fixes the issue where the dart_plugin_registrant.dart file is not generated correctly.

Tested this locally with packages referenced by path. When I increased the Flutter SDK version to 2.11 then the issue we saw in #1270 was gone.

Related Issues

• Fix: [Bug]: No implementation found for method getAll on channel dev.fluttercommunity.plus/package_info #1270
• Related: Enable inline Dart plugin implementation on Desktop flutter/flutter#96610
• Related: Missing calls to "registerWith()" in generated dart_plugin_registrant.dart flutter/flutter#113720
• Related: [Question]: Is generated_plugin_registrant.dart necessary for web for device_info_plus and package_info_plus? #1274

Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• I titled the PR using Conventional Commits.
• I did not modify the CHANGELOG.md nor the pubspec.yaml files.
• All existing and new tests are passing.
• The analyzer (flutter analyze) does not report any problems on my PR.

Breaking Change

Does your PR require plugin users to manually update their apps to accommodate your change?

• Yes, this is a breaking change (please indicate that with a ! in the title as explained in Conventional Commits).
• No, this is not a breaking change.

[miquelbeltran]

Since we are at it, I have also upgraded the platform interfaces (although not required for this fix) and removed some of the SDK requirements from the examples, as they are not required.

[CodeDoctorDE]

Why do we need the platform_interface packages if we only need one package for every platform?

[miquelbeltran]

Why do we need the platform_interface packages if we only need one package for every platform?

It has been a long discussion in the maintainers team, and the conclusion is that having a package interface as an external package allows for expandability. I'd personally get rid of it but not everyone agreed.

[vbuberen]

This is great that we are pushing things a little bit and getting rid of these really old versions as well as bumping all plugins at once, getting rid of differences in min supported version.