- We don't need the Threads target workaround anymore, that breaks the
build with Qt6 even.
- The Gradle wrapper shipped with Qt is no longer installed as executable,
so we need to run this in sh explicitly.
- Qt6 uses a different Android Gradle plugin version (not to be confused
with the Gradle version), which we need to make available for the
configure_file() call on the build.gradle file.

With this most Framework modules build against Qt6 here.

The relevant issue is only fixed in 23

I was seeing `error: No such remote 'origin'` in the cmake output.
This commit avoids hardcoding `origin` as the upstream URL and instead
uses the `git rev-parse @{u}` to get the configured upstream.

As a follow-up we may want to check if this should be executed by default,
but for now this fixes a warning that I'm seeing with various projects.

And the generated html looks more correct

GIT_SILENT

This fixes spurious differences after a roundtrip through Google Play,
breaking change detection and thus triggering unnecessary metadata
updates.

This considerably simplifies comparing our data with that retrieved from
Google Play for automatically syncing metadata.

Qt maps it this way