Attempt to use gradle wrapper for cache cleanup

[bigdaz]

The cache-cleanup operation works by executing Gradle on a dummy project and a custom init-script. The version of Gradle used should be at least as high as the newest version used to run a build.

Previously, if the Gradle version on PATH didn't meet this requirement, the action would download and install the required Gradle version.

With this PR, the action will now use an existing Gradle wrapper distribution if it meets the requirement. This avoids unnecessary downloads of Gradle versions that are already present on the runner.

The logic is:

• Determine the newest version of Gradle that was executed during the Job. This is the 'minimum version' for cache cleanup.
• Inspect the Gradle version on PATH and any detected wrapper scripts to see if they meet the 'minimum version'.
• The first executable that is found to meet the requirements will be used for cache-cleanup.
• If no executable is found that meets the requirements, attempt to provision Gradle with the 'minimum version'.

Fixes #515

[github-actions]

Job Summary for Gradle

Demo adding Build Scan® comment to PR :: successful-build-with-always-comment

Gradle Root Project	Requested Tasks	Gradle Version	Build Outcome	Build Scan®
kotlin-dsl	build	8.12	✅