Allow all Clojure tasks to specify a JavaLauncher. This is part of Gradle's JVM toolchain [1] feature allowing decoupling the JVM version Gradle uses from the JVM used for tasks.

Now all tasks Clojurephant provides have a common base interface ClojureTask the support fork options and java launcher.

This also picks up the JavaToolchain on the JavaPluginExtension and applies it by default to all ClojureTasks.

Fixes #174

[1] https://docs.gradle.org/current/userguide/toolchains.html
Add JavaLauncher to all tasks

Related issues:

Contributor Checklist

• Review Contributing Guidelines.
• Commits contain discrete changes, messages include context about why the change was made and reference the relevant issues.
• Commit messages should be prefixed with one of the following (these are used to determine the next version we release):
  • patch: if the change added no new functionality and is backwards compatible
  • minor: if the change added new functionality and is backwards compatible
  • major: if the change is not backwards compatible
  • chore: if the change doesn't affect plugin logic/behavior at all (and obviously still backwards compatible)
  • Any of these can optionally specify an area of the plugin they affected in parentheses (e.g. patch(clojurescript): )
    • build
    • docs
    • clojure
    • clojurescript
    • common
    • repl
• Provide functional tests. (under clojurephant-plugin/src/compatTest)
• Update documentation for user-facing changes. (under docs/)
• Ensure all verification tasks pass locally. (./gradlew check)
• Ensure CI builds pass on all Java versions. (watch the checks tab once the PR is opened)

TIP: If troubleshooting a CI failure, look for the build scan URL in the workflow run summary.