gradle: excluding spotlessJava should also exclude spotlessApply

When running `gradle compileJava -xspotlessJava`, `spotlessApply` will still run. Since `spotlessApply` copies files from build/spotless/spotlessJava to the source tree, this can overwrite unsaved work in progress, making teams **lose valuable work** due to a simple misunderstanding. Since this is a silent overwrite, team might also not notice that changes have been made, allowing **bugs to enter the codebase**.

`spotlessApply` should only ever run when the files it copies were created as part of the same build, to ensure no work is lost.

This happened on a company project, so I cannot quickly produce a public repo, but I could if need be. The steps to reproduce would be (in a java project using the spotless plugin...):

```
git clone ...
cd ...
// assuming this will have some file that can be formatted
./gradlew compileJava
git reset --hard
git checkout other_branch
// assuming some file from earlier branch is different here

./gradlew compileJava -xspotlessJava
git diff
```

The last git diff should not have any changes. However, currently for me this overwrites the source file with the spotless output from the ./gradlew compileJava task.

Using gradle8, java17, spotless 6.25.0 on MacOs.

Inizia riproducendo la sequenza segnalata in un progetto Java usando Gradle, Java 17 e Spotless 6.25.0, in particolare `./gradlew compileJava -xspotlessJava` seguito da `git diff`. Esamina come sono collegati `spotlessJava` e `spotlessApply`; il lavoro è considerato completato quando l’esclusione di `spotlessJava` lascia invariato l’albero dei sorgenti.

Scritto dal modello di indicizzazione a partire dal testo della issue.