This plugin is API based instead of functionality based #56

Note
Issue created in favor of the Flutter docs and their recommended post by Mehmet Fidanboylu.

The issue is in the core of this plugin:

In 2021 I created this plugin just to allow access to one, two methods available on Android APIs, so I thought that's was fine to create a plugin fully-based on native APIs. But since the package grown and people wanted to add support to another features I noticed two issue:

• It's impossible to a plugin follow all Android APIs maintained only by one developer.
• Kotlin != Dart and Flutter != Android. That is:

APIs don’t match across platforms and you are forced to expose an intersection of the API often with crippling consequences…
- Mehmet Fidanboylu.

• Missing tests. This one is probably the critical one.

So the following actions will be taken to the next major release:

• Deprecate all mirror APIs.
• Keep/add feature-based APIs.
• Add support for iOS.

Requirements/Recommended technical fixes:

• Convert this plugin to a Federated plugin already mentioned in Convert plugin to a federated plugin #39.
• Test plugin (Platform-side).

That's all folks!