Add support for Android 11 new privacy settings

[lbalmaceda]

Changes

When this library is used on Android 11, the new privacy rules kick in preventing our CustomTabsController class to query for browser apps in order to pick the best candidate. The result is a failure, or an automatically cancelled authentication. By using the latest Android Gradle Plugin patch and adding the "queries" tag in the library's manifest, the final manifest

The lint-ignore rule at the top of the manifest is required until we target SDK 30. In order to do that, we need to migrate to and support AndroidX.

Compiling: For anyone running into compiling issues where the "queries" tag in the manifest is not a valid tag, that's because your app is using an old version of the Android Gradle Plugin that still doesn't have support for queries. Check the link below to learn to what version you should update.

References

• Android Gradle Plugin versions with support for the manifest's "queries" tag: https://android-developers.googleblog.com/2020/07/preparing-your-build-for-package-visibility-in-android-11.html
• Checking available browsers query (Recipe): https://developer.android.com/preview/privacy/package-visibility-use-cases#check-browser-available
• Fixes No installed browser found on Pixel device with Android 11 #319

Testing

I've tested this on a separate sample app that targets SDK 30. As seen in the attached screenshot, bottom right, the "queries" tag is added to the merged manifest file and comes from the changes on this PR.

I've also tested this when the sample app defines its own set of queries. And both turn out to be merged correctly, without the need to use any special node annotation.

Checklist

• I have read the Auth0 general contribution guidelines

• I have read the Auth0 Code of Conduct

• All existing and new tests complete without errors