Bump target SDK to Android 12 (31)

[abelgardep]

We should bump the compileSdk and targetSdk to 31 since there are some dependencies that require those versions.

To do it, we need to verify that the ownCloud App supports each point in https://developer.android.com/about/versions/12/behavior-changes-12

TASKS

• Research (if needed)
• Create branch feature/feature_name
• Research which Android12 features must be checked inside the app, due to feasible changes.
• Development tasks
  • Develop changes
  • ...
• Code review and apply changes requested
• Design test plan
• QA
• Check if in is installable from Internal testing track in Android 12
• Merge branch feature/feature_name into master

PR

• App
• Library (if needed)

[hannesa2]

This is my attempt #3512

[fesave]

Apps targeting API 31+

Behaviour changes

User experience

• Custom notifications
• Android App Links verification changes - No impact on us
• PiP Mode - No impact on us
• Toast redesign

Security and privacy

• Approximate location - No impact on us
• Modern SameSite cookies in WebView
• Motion sensors are rate-limited - No impact on us
• App hibernation
• Attribution declaration in data access auditing - No impact on us
• ADB backup restriction - No impact on us
• Safer component exporting
• Pending intents mutability
• Unsafe intent launches

Performance

• Foreground service launch restrictions
• Exact alarm permission - No impact on us
• Notification trampoline restrictions

Backup and restore

• D2D transfer functionality changes - No impact on us
• New include and exclude format - No impact on us

Connectivity

• Concurrent Peer-to-Peer + Internet Connection - No impact on us
• mDNSResponder native API - No impact on us

Vendor libraries

• Vendor-supplied native shared libraries - No impact on us

Updated non-SDK restrictions

• Tests

[fesave]

After performing an examination of the .apk with the tool provided by Google to check how many non-SDK interfaces are currently in the project, this is the result:

65 hidden API(s) used: 10 linked against, 55 through reflection:

 - 48 in unsupported
 - 2 in blocked
 - 1 in max-target-o
 - 11 in max-target-p
 - 3 in max-target-q
 - 0 in max-target-r

By consulting the table that Google published from API 29, we can deduce that:

Most of our APIs are not supported, but currently, they are not restricted and our application can use them, we have to be careful with them in case they change and make the app not work properly.

What do you think @abelgardep @jesmrec @theScrabi ?