ci: disable Gradle config cache at the property level (fix JS NPM config-time resolution)

CI's Build & Test failed with:
  java.lang.RuntimeException: Configuration 'jsTestNpmAggregated' was resolved
  during configuration time.

Root cause (gradle#31483): KGP's KotlinPackageJsonTask resolves the JS
`*NpmAggregated` configs at configuration time; AGP's DependencyResolutionChecks
— installed when the Gradle configuration cache feature is ENABLED — rejects
that on a cold CI configuration. build.yml passes `--no-configuration-cache`,
but ci-gradle.properties set `org.gradle.configuration-cache=true`, so the check
was still installed and the CLI override did not reliably suppress it (the
failure is intermittent: it surfaces on cold-config task-graph traversal, which
is why earlier runs went green).

Set `org.gradle.configuration-cache=false` in the CI gradle.properties so the
feature (and thus AGP's strict check) is genuinely off in CI, matching build.yml's
documented intent. Local dev keeps config cache ON via the repo gradle.properties.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: michalharakal

.github/ci-gradle.properties

@@ -4,7 +4,14 @@ org.gradle.workers.max=2
 # Disable parallel execution to reduce memory pressure and AAPT2 flakiness
 org.gradle.parallel=false
 org.gradle.caching=true
-org.gradle.configuration-cache=true
+# Config cache OFF in CI (genuinely, at the property level — not just via the
+# `--no-configuration-cache` CLI flag in build.yml). With it ON, AGP's
+# DependencyResolutionChecks is installed and rejects KGP's KotlinPackageJsonTask
+# resolving the JS `*NpmAggregated` configs at configuration time on a cold build
+# (`Configuration 'jsTestNpmAggregated' was resolved during configuration time`),
+# which the CLI override does not reliably suppress. See gradle#31483. Local dev
+# keeps config cache ON via the repo gradle.properties.
+org.gradle.configuration-cache=false
 
 # Memory tuning
 org.gradle.jvmargs=-Xmx4g -Dfile.encoding=UTF-8