feat: bump targetSdkVersion from 30 to 31, and to 32

[KazuCocoa]

Lets try to use newer targetSdkVersion

AS has helpful feature to show suggestions we should fix in the upgrade. According to the hint, we should:

Bluetooth is the manifest update.

The 2nd one is https://developer.android.com/topic/performance/app-hibernation :

If your app targets Android 11 (API level 30) or higher, and the user doesn't interact with your app for a few months, the system places your app in a hibernation state. The system optimizes for storage space instead of performance, and the system protects user data. This system behavior is similar to what occurs when the user manually force-stops your app from system settings.

so maybe not related to the uia2 server.

The 3rd one is may not for the case. Possibly our settings app needs some update though.

The 4th one https://developer.android.com/about/versions/12/behavior-changes-12#notification-trampolines

To improve app performance and UX, apps that target Android 12 or higher can't start activities from services or broadcast receivers that are used as notification trampolines. In other words, after the user taps on a notification, or an action button within the notification, your app cannot call startActivity() inside of a service or broadcast receiver.

Maybe we do not have the usage to start UIA2 server from the notification regularly.

After upgrading to 31, checked 32. Then no diffs as below, so i have bumped to 32 as well.

[KazuCocoa]

i have manually checked the build on my local with android 11 and 12 real devices with simple get page source, find element and send keys

[github-actions]

🎉 This PR is included in version 5.13.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀