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+**

Commencez par le commentaire lié et Spotless #986, qui décrivent l’API de configuration-cache JVM-local proposée et le workaround. L’issue ne nomme aucun fichier ni test, et la prise en charge de Gradle demandée est en dehors de ce dépôt ; l’edit indique que la prise en charge complète de no-asterisk est déjà disponible dans Spotless 7.0.0+.

Rédigé par le modèle d'indexation à partir du texte de l'issue.