Avoid check of the ratchetFrom branch when Spotless not invoked

Currently, Spotless (Gradle Plugin) performs a check for the presence of the ratchetFrom branch on every command execution. This includes instances where Spotless-specific commands aren't called, which can lead to unnecessary checks, and adds the workaround (e.g. git fetch depth:0) for all cases.

Could we refine the ratchetFrom functionality so that it checks for branch presence only when a Spotless command is actually invoked?

I believe this adjustment could be beneficial for users who integrate Spotless into their development workflows, ensuring that the tool remains as efficient and unobtrusive as possible.

Inizia tracciando la gestione di ratchetFrom nello Spotless Gradle Plugin e il modo in cui vengono invocati i comandi specifici di Spotless. Verifica che il controllo della presenza del branch avvenga solo quando viene eseguito un comando Spotless, mentre i normali comandi Gradle evitano tale controllo e il workaround di fetch-depth che ne deriva.

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