ClearConfigurationCacheStateMutator incorrectly hardcodes the location of configuration-cache

[liutikas]

  @Override
    protected void cleanup() {
        System.out.println("> Cleaning configuration cache state");
        cleanup(new File(projectDir, ".gradle/configuration-cache"));
        cleanup(new File(projectDir, ".instant-execution-state"));
    }

for projects that use --project-cache-dir / org.gradle.projectcachedir the configuration cache will be in a different location. So the gradle-profiler should either read the project cache dir state that is set or set a custom one to make sure the location is where it is expected.

[liutikas]

The way it will manifest in the projects today is that if you have

rerunDryRun {
    tasks = ["bOS"]
    gradle-args = ["--dry-run", "--rerun-tasks"]
    daemon = cold
    warm-ups = 1
    clear-configuration-cache-state-before = BUILD
}

you'll see

* Running measured build #1
> Cleaning configuration cache state
Configuration on demand is an incubating feature.
Reusing configuration cache.

which will attempt to delete configuration cache, do nothing, reuse configuration cache from a previous run.

[bamboo]

I think It would make more sense for gradle-profiler to set --project-cache-dir since it already changes the Gradle user home for isolation.