chore(android_alarm_manager_plus): using super.key parameter to resolve linting issues

[OutdatedGuy]

Description

Using the recommended super.key parameter instead of the super() constructor in Widgets.

They do not pose any issue while using the package, but while fixing another issue in one of the packages I saw these linting warnings and thought of fixing them.

Related Issues

Trivial changes so doesn't need an issue.

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.

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]

Thanks for the contributions (this and the other PRs)!

I'll be taking a look at them and merging/closing them.

Meanwhile, please address the request for change I mentioned.

[miquelbeltran]

I would also need that the lint fixes are separated per package. If possible, one PR per package, so at the end there is one squashed commit per package.

[OutdatedGuy]

I would also need that the lint fixes are separated per package. If possible, one PR per package, so at the end there is one squashed commit per package.

Trivial changes like this can be committed from a single PR across many packages as they surely does not break or change any working in the code.

Please check if having multiple PRs is really necessary and let me know what to do.

[miquelbeltran]

Yes, we prefer if the PRs are per package because that facilitates generating changelogs.

[OutdatedGuy]

Okay, fair enough reason 👍🏼

[miquelbeltran]

Waiting for CI to complete to merge