Fall back to java.jdt.ls.java.home if embedded JRE fails

When deploying VSCode to an AP Computer Science lab where the students don't have admin privileges, attempts to enable the latest Extension Pack for Java (which includes the “Language Support for Java(TM) by Red Hat” extension) fail reporting “Couldn’t start client Language Support for Java” whenever they open a Java project.

Environment

• Operating System: Windows 10
• JDK version: Various (tried latest Microsoft OpenJDK 11 & 17 as well as those from Adoptium's Teemurin)
• Visual Studio Code version: 1.64.0
• Java extension version: v 1.1.0 through v1.3.0

Steps To Reproduce

1. Install latest VSCode and JDK (with JAVA_HOME set correctly)
2. Create a new Java class

Current Result

Reports “Couldn’t start client Language Support for Java” when trying to run or debug the Java code.

Expected Result

Should work like it does for users with admin privileges (or how it did for v1.0.0).

Additional Information

Works fine for users with admin privileges or if we roll the students back to v1.0.0 of this extension. Typing java -version in terminal returns correct OpenJDK version.

Iniziare riproducendo il problema su Windows 10 con un progetto Java e confrontare il percorso della JRE incorporata con l'impostazione java.jdt.ls.java.home. Verificare il comportamento per gli utenti senza privilegi di amministratore e con JAVA_HOME configurato. Il lavoro è completato quando il client Language Support for Java si avvia e il codice Java può essere eseguito o sottoposto a debug senza richiedere l'accesso di amministratore.