Upgrade Android gradle plugin

[tustanivsky]

This PR is supposed to address Android symbol upload issues that some Sentry self-hosted users faced previously due to the legacy gradle plugin being in use (i.e. #502).

In order to bump the Android gradle plugin version it was necessary to override engine's gradle version as well by replacing gradle-wrapper.properties file in build dir.

[github-actions]

	Messages
📖	Do not forget to update Sentry-docs with your feature once the pull request gets approved.

Generated by 🚫 dangerJS against d7d15e1

[bitsandfoxes]

Is that change intentional? The how do the LinuxIntermediate related to Gradle?

[tustanivsky]

Yes, aside from adding Gradle here I've also removed LinuxIntermediate stuff which is now redundant (probably I've missed deleting these entries earlier). Should we tackle this kind of clean-up in a separate PR?

[bitsandfoxes]

That's the gradle tool itself, right? And that's a requirement for the sentry-android-gradle-plugin 4.11.0?
Are we going to mess with user's build by messing with the gradle version that comes with the UE installation?

[tustanivsky]

Yes, the io.sentry.android.gradle >= 3.0.0 requires Android Gradle Plugin >= 7.0.0 according to docs.
I've tested this with a few different engine versions (including pretty old UE 4.27) and the build was successful however there's always a chance that some compatibility issues with 3rd-party plugins can arise.

[tustanivsky]

UPD: Added new plugin setting which allows switching back to legacy Sentry Android Gradle plugin in case of any compatibility issues with other third-party plugins

[bitsandfoxes]

I'm not sure I see how this fixes the issue linked. The issue was resolved by adding the defaults url, right? How does the newer Android Gradle Plugin help with this? Is there anything else we're getting out of it?

The fallback is great, I really appreciate it, changing the user's Gradle version still makes me nervous.

[bitsandfoxes]

Is the hardcoded version number going to bite us in the butt later on?

[tustanivsky]

Since we don't have any means allowing to check how Sentry Gradle plugin performs in our CI probably it'd be safer to keep a hardcoded version here instead of bumping it automatically for the time being.

[tustanivsky]

I'm not sure I see how this fixes the issue linked. The issue was resolved by adding the defaults url, right? How does the newer Android Gradle Plugin help with this? Is there anything else we're getting out of it?

With the newer Gradle plugin version adding defaults.url to sentry.properties when using Sentry self-hosted shouldn't be required any longer. It was a legacy issue but now the right URL can be extracted from the authentication token so users won't face the problem with uploading symbols.

[bitsandfoxes]

Considering that we cannot offer ootb support for self-hosted and there is a fallback/opt-out for those that need it: LGTM! 🔥