[aot repositories] refresh AOT metadata fails when terminal process has different JVM

Clicking on the Refresh AOT metadata code lens causes a build to be executed on the terminal, but that fails if the project uses a more recent JDK than what is being used by default in the terminal. In my case, I had JDK 21 set as the default in the terminal (on my macOS system in general, not specific to VSCode), but the project was configured to use Java 25. As a result, the build to refresh the AOT metadata failed.

We maybe need to use the project configuration to at least check whether the JDK that the terminal uses is compatible with what the project requires.

Not surf through whether we can go one step further and identify the correct JDK to use to run the build. Maybe we could infer that from the JDK-related classpath entries from the project.