feat(android_alarm_manager_plus)!: Change Android compile SDK, update Android build config

[vbuberen]

Description

The initial idea was to just do a bump to compile SDK 36, but decided to not do it and use flutter.compileSdkVersion. It should make us worry less about skipping Android version, like it happened with SDK 35.
At the same time I didn't want us to be strict with minSDK, so left it 21 as Flutter supported before 3.35.x release.

As to rest of changes in dependencies - it is an alignment with dependencies versions used by official Flutter packages (e.g. https://github.com/flutter/packages/blob/main/packages/shared_preferences/shared_preferences/example/android/settings.gradle ). I believe that such change should help with better compatibility across the pub ecosystem.

Additionally, thanks for Android Gradle Plugin bump we are preparing plugins to be compatible with apps moving to Android 16KB memory pages: https://developer.android.com/guide/practices/page-sizes

Marking this PR as breaking, because I am sure there will be lots of users, who will struggle with checking the requirements and adjusting Android part of their projects accordingly.

Next up I will create similar PRs for the rest of plugins in the repo.

Related Issues

• Part of [Request]: Bump compile SDK of all plugins to 36 (Android 16) #3624
• Part of [Request]: Android 16Kb page size support #3649
• Supersedes chore(deps): bump permission_handler from 11.4.0 to 12.0.1 in /packages/android_alarm_manager_plus/example #3617

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.

[ekuleshov]

@vbuberen stating this is at very least very hostile to all users of the plus plugins.

...I am sure there will be lots of users, who will struggle with checking the requirements and adjusting Android part of their projects accordingly.

The best practice for a major version bump like that is to provide some migration guidelines in a plugin's readme