Update CI to Java 17 and restore Gradle wrapper compatibility

[Copilot]

The failing Test workflow was still provisioning Java 11 even though the build now requires Java 17+. This updates the CI runtime to match the build requirements and restores a Gradle wrapper version that remains compatible with the current IntelliJ Gradle plugin.

• Root cause

  • actions/setup-java in CI pinned the job to Java 11
  • Gradle then failed immediately with:

    Gradle requires JVM 17 or later to run. Your build is currently configured to use JVM 11.
    

• Workflow updates

  • move both Test and Release workflows to actions/setup-java@v5
  • provision Temurin Java 17 explicitly in each workflow

• Build compatibility

  • revert the Gradle wrapper from 9.7.1 to 8.0
  • keep the wrapper aligned with the repository’s current org.jetbrains.intellij plugin line, which is not compatible with Gradle 9

• Result

  • CI now uses the required JVM version
  • the workflow configuration and wrapper version are consistent with the project’s current build stack

[funivan]

@copilot update gradle to latest compatible version

[Copilot]

@copilot update gradle to latest compatible version

Updated in aa9c0a3 to Gradle 8.14.5, the latest Gradle 8.x release that remains compatible with the current org.jetbrains.intellij 1.17.4 plugin line.

[funivan]

@copilot can we upgrade jvm to latest version and gradle to the latest one ?

[Copilot]

@copilot can we upgrade jvm to latest version and gradle to the latest one ?

Updated in 13d90e6. CI now runs on Temurin 25, the wrapper is back on Gradle 9.7.1, and the build was migrated to org.jetbrains.intellij.platform 2.x so the latest Gradle line is supported while the plugin bytecode target stays on Java 17 for IDE compatibility.