build: use standardized Gradle Daemon toolchain [JetBrainsRuntime/21]

[david-allison]

• https://github.com/JetBrains/JetBrainsRuntime
• Version 21

Purpose / Description

Android Studio proposed doing this, aligning the CLI and in-IDE invocations of gradle, and aligning the toolchain across developer machines.

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.

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

Fixes

• Fixes Standardize Gradle Daemon toolchain using Gradle Daemon JVM Criteria #20382

Approach

• Open Android Studio
• Click 'Migrate'
• Read a lot of documentation, gathering sources. My conclusion:
  • Standardizing the toolchain should help onboarding.
  • Using the JetBrains runtime seems like a sensible JVM default: https://github.com/JetBrains/JetBrainsRuntime
  • If there are issues, we can revert this with little fallout

How Has This Been Tested?

Trusting CI, project appears to still build and run

Learning

• https://developer.android.com/studio/releases/past-releases/as-panda-1-release-notes#daemon-jvm-criteria
• https://docs.gradle.org/current/userguide/gradle_daemon.html#daemon_jvm_criteria
• https://plugins.gradle.org/plugin/org.gradle.toolchains.foojay-resolver-convention
• https://github.com/gradle/foojay-toolchains
• https://api.foojay.io/swagger-ui/
• https://discuss.gradle.org/t/how-to-use-version-catalog-in-the-root-settings-gradle-kts-file/44603

Checklist

• You have a descriptive commit message with a short title (first line, max 50 chars).
• You have commented your code, particularly in hard-to-understand areas
• You have performed a self-review of your own code
• UI changes: include screenshots of all affected screens (in particular showing any new or changed strings)
• UI Changes: You have tested your change using the Google Accessibility Scanner