fix(battery_plus): Implement not charging battery state

[codercengiz]

Description

Normally, there are 5 different states to define the battery state on the Android side:
https://developer.android.com/reference/android/os/BatteryManager#BATTERY_STATUS_CHARGING
full, charging, discharging, not _charging, unknown. But in the current code base, discharging and not_charging are considered the same, and both are parsed as discharging.
With this change, if the Android SDK has a not_charging state, the Flutter side will also see this state.

On Samsung phones, if we enable battery protection, the phone charges up to 85%. When it reaches 85%, the status changes from charging to not_charging. When I checked, the current used is almost 0 mA.

Related Issues

Fix #2274

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 plugin version in pubspec.yaml files.
• All existing and new tests are passing.
• The analyzer (flutter analyze) does not report any problems on my PR.

[vbuberen]

Thanks for your contribution, but I can't accept this PR as it is only covering Android platform.
If you would have really read the contribution guide instead of just setting such checkmark in PR template you would see that new features covering one platform can't be accepted: https://github.com/fluttercommunity/plus_plugins/blob/main/CONTRIBUTING.md#-cannot-be-accepted

[dkbast]

I think what @vbuberen was trying to say is, that we appreciate the work that you have done, but that we have decided to only accept PRs that provide feature parity for the mobile platforms. As such you (or someone else) would need to add the same functionality for iOS for this PR to move out of a draft status and into the review phase. @codercengiz are you planning on creating an iOS implementation as well?

[vbuberen]

I think what @vbuberen was trying to say is, that we appreciate the work that you have done, but that we have decided to only accept PRs that provide feature parity for the mobile platforms.

There were no request to translate or interpret what I wrote there.

Also, I would ask you to not use we and not reply on behalf of Plus Plugins maintainers, because except being added to a chat on this topic there were no activity or contributions from you. Thus, please speak for yourself.

[vbuberen]

are you planning on creating an iOS implementation as well?

This can't be added because currently iOS has no separate state for not_charging like Android OS has: https://developer.apple.com/documentation/uikit/uidevice/batterystate

[dkbast]

@vbuberen if it cannot be added to iOS, imho this would imply that this PR is already feature complete, because, even if a feature cannot be added for all platforms it should still be ok to add it to the ones which support it. If I remember correctly thats how it is handled in some of the other plugins.

[vbuberen]

I would like to do some tests to check a few assumptions first. Will get back to this PR later today when have more time.

[vbuberen]

After an additional research I found out that there is a possibility to implement same connected, but not charging state on MacOS as well, so updating platform interface enum with new item would be used not only by Android. Based on this fact I would like to accept this PR and merge it. Afterwards I will implement MacOS version and release an update when it is ready.