ci: opt out of AGP config-time dependency-resolution check (real fix for JS NPM)

My previous commit (config-cache=false) was the wrong lever — the check still
fired. The throw is com.android.build.gradle.internal.DependencyResolutionChecks
(registerDependencyCheck), which AGP installs independent of the config cache and
which rejects KGP's KotlinPackageJsonTask resolving the Kotlin/JS + Wasm
`*NpmAggregated` configs at configuration time (gradle#31483). transformers has
real JS npm deps (ktor-client-js, kotlinx-browser) so this resolution happens;
the engine repo runs the same `assemble allTests` green only because it has none.

Revert config cache to true (matches the engine CI; not the cause) and set
`android.dependencyResolutionAtConfigurationTime.disallow=false` to opt out of
AGP's check, letting the JS npm resolution proceed as it does off-CI.

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

Author: michalharakal

.github/ci-gradle.properties

@@ -4,14 +4,7 @@ org.gradle.workers.max=2
 # Disable parallel execution to reduce memory pressure and AAPT2 flakiness
 org.gradle.parallel=false
 org.gradle.caching=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
+org.gradle.configuration-cache=true
 
 # Memory tuning
 org.gradle.jvmargs=-Xmx4g -Dfile.encoding=UTF-8
@@ -23,3 +16,13 @@ kotlin.compiler.execution.strategy=daemon
 
 # Disable AAPT2 daemon to prevent "daemon unexpectedly exit" crashes
 android.aapt2.daemon=false
+
+# AGP's DependencyResolutionChecks (com.android.build.gradle.internal) fails the
+# build when a configuration is resolved at configuration time. KGP's
+# KotlinPackageJsonTask resolves the Kotlin/JS + Wasm `*NpmAggregated` configs at
+# config time (we DO have JS npm deps: ktor-client-js, kotlinx-browser), so on a
+# cold CI build it throws `Configuration 'jsNpmAggregated' was resolved during
+# configuration time` (gradle#31483). It's a false positive against KGP's known
+# behaviour — the engine repo doesn't hit it only because it has no JS npm deps.
+# Opt out of AGP's check so the JS npm resolution proceeds as it does off-CI.
+android.dependencyResolutionAtConfigurationTime.disallow=false