Auto detect JVM toolchains in standard locations on GitHub runners

[JavierSegoviaCordoba]

The issue on the Gradle repo: gradle/gradle#14903

Current workaround:

      - name: Create Gradle files
        run: |
          cd ~
          mkdir -p .gradle/ && touch .gradle/gradle.properties

      - name: Set up Java
        id: setup-java
        uses: actions/setup-java@v3
        with:
          distribution: 'zulu'
          java-version: 11

      - name: Setup Gradle Java installations paths
        run: |
          cd ~/.gradle
          echo "org.gradle.java.installations.paths=${{ steps.setup-java.outputs.path }}" >> gradle.properties

      - name: Setup Gradle
        uses: gradle/gradle-build-action@v2

[joffrey-bion]

Given that it's less easy to get the output from setup-java by default in the gradle-build-action, I think a good starting point would be to at least make Gradle aware of the pre-installed Java distributions through this action.

GitHub currently provides all current LTS versions in the hosted tools cache, and it provides env variables to each of their locations, based on the major version. At the time of writing, those are: JAVA_HOME_8_X64, JAVA_HOME_11_X64, and JAVA_HOME_17_X64 (see the runner environment doc).

So I believe a good starting point would be for this action to pass by default a CLI argument that makes Gradle aware of those env variables, such as:

-Porg.gradle.java.installations.fromEnv=JAVA_HOME_8_X64,JAVA_HOME_11_X64,JAVA_HOME_17_X64

This has the drawback of ignoring this property from the project's gradle.properties, so we could mitigate this by providing an option to disable this behaviour. WDYT?

[bigdaz]

It turns out this was mostly working out of the box.

On all runners, toolchains provisioned via setup-java are added to the Maven Toolchains definition, and Gradle will detect based on this information.

On ubuntu-latest and `macos-latest' the pre-installed JDKs are symlinked into standard locations, and so are detected by Gradle.

But on windows-latest the pre-installed JDKs are not detected.