Stale object files and binaries should be removed when the Gradle version changes

Currently, task history is lost when changing Gradle versions and this can lead to stale object files and binaries being left behind in output directories. This might happen, for example, due to source files being removed or renamed or changes to the binary names that happen after the version change. It can also happen due to changes to the algorithm that calculates the output location of a particular object file or binary.

Gradle should use the same approach to clean up stale object files and binaries as is used to clean up stale class files (whatever that happens to be at the time of implementation).

Just to note: Gradle currently supports cleaning up stale object files as source files are removed or renamed when the Gradle version does not change. It does not support cleaning up stale binaries when the names change.

The issue does not identify any files, tests, or entry points. Start by locating the existing stale class-file cleanup mechanism, then determine how the same behavior should cover native object files and binaries after a Gradle version change; done means stale outputs from removed, renamed, or relocated sources are removed.

Written by the indexing model from the issue text.