build: use standardized Gradle Daemon toolchain

using Gradle Daemon JVM Criteria: [JetBrainsRuntime/21]

This change was performed by Android Studio

https://developer.android.com/studio/releases/past-releases/as-panda-1-release-notes#daemon-jvm-criteria

I committed `gradle-daemon-jvm.properties` as it was done so in gradle:
https://github.com/gradle/gradle/commits/master/gradle/gradle-daemon-jvm.properties

This file standardizes the project, so invocations will use:
* https://github.com/JetBrains/JetBrainsRuntime
  * source: https://api.foojay.io/disco/v3.0/distributions
* toolchainVersion: 21

> Projects using Daemon toolchain allow builds to automatically detect
> installed toolchains given the defined JVM criteria or download a compatible
> one if cannot be found locally.
> In addition, using the Daemon toolchain aligns the selection between CLI and
> IDE, avoiding spawning multiple Daemons improving performance but also makes
> it simple to handle the required toolchain on different machines.

My conclusions:

* Standardizing the toolchain should help onboarding.
* Using the JetBrains runtime seems like a sensible JVM: https://github.com/JetBrains/JetBrainsRuntime
* If there are issues, we can revert this with little fallout

Glossary:
foojay: Friends of OpenJDK
Disco: Discovery API

Docs:
https://developer.android.com/studio/releases/past-releases/as-panda-1-release-notes#daemon-jvm-criteria
https://api.foojay.io/swagger-ui/
https://plugins.gradle.org/plugin/org.gradle.toolchains.foojay-resolver-convention
https://docs.gradle.org/current/userguide/gradle_daemon.html#daemon_jvm_criteria

Fixes 20382