Petition Gradle to support JVM-local configuration-cache

***Please thumbs-up this issue if you'd like Gradle to build this.*** TLDR: Unlike remote build cache, configuration cache is never going to be relocatable. Because of that, it might as well be a JVM-local cache (within-daemon), which removes the performance and incidental-complexity penalties of a serialization roundtrip. Spotless #986 hacks a workaround to demonstrate this approach, example API in [comment below](https://github.com/diffplug/spotless/issues/987#issuecomment-963664602). Gradle could support this natively so that configuration cache is faster to use and easier to develop plugins against.

**EDIT: full no-asterisk support for configuration cache is available in Spotless 7.0.0+**

Start with the linked comment and Spotless #986, which describe the proposed JVM-local configuration-cache API and workaround. The issue does not name a file or test, and its requested Gradle support is outside this repository; the edit says full no-asterisk support is already available in Spotless 7.0.0+.

Written by the indexing model from the issue text.