[codex] Fix Gradle toolchain provisioning

[ansman]

Summary

Fixes snapshot deployment failing when Gradle needs to resolve the Java 23 Azul toolchain on a clean GitHub Actions runner.

• Applies the Foojay resolver convention in the included build-logic build so its own Java/Kotlin toolchains can be auto-provisioned.
• Configures updateDaemonJvm to generate daemon JVM criteria for Java 23 with the Azul vendor.
• Regenerates gradle/gradle-daemon-jvm.properties so daemon auto-provisioning uses Azul download URLs and records toolchainVendor=AZUL.

Root cause

The snapshot job ran with Java 21 but the build requests a Java 23 Azul toolchain. Gradle could not find that local installation and reported that toolchain download repositories were not configured for that build path.

Validation

• ./gradlew updateDaemonJvm --no-daemon --stacktrace
• env GRADLE_USER_HOME=/private/tmp/auto-dagger-gradle-home ./gradlew publishSnapshot --no-configuration-cache --stacktrace -m -PmavenCentralUsername=dummy -PmavenCentralPassword=dummy
• ./gradlew check --continue --stacktrace reached all Kotlin/Android tests and lint, but failed on local :checkPython because the selected local Python has no pip installed.