Feature request: Launch configuration option to force Java execution environment used for run/debug

Feature request: Please add a way to force a specific Java execution environment (from the environments defined by "java.configuration.runtimes") to be used by the debugger to launch the application.

For compatibility reasons, the Maven project files defines "1.8" as "<java-version>". However, in several environments (HiDPI), the use of at least Java 11 is required to run the application correctly. At the moment, there seems to be no way to force the VSCode Java debugger to use Java 11 and overwrite the "<java-version>" setting from the Maven POM file.

Environment

• Operating System: Windows 10
• JDK version: Java SE 1.8 and Java SE 11
• Visual Studio Code version: 1.49.1
• Java extension version: 0.10.0
• Java Debugger extension version: 0.28.0

Current Result

Visual Studio Code Java debugger is always launching using Java SE 1.8.

Expected Result

Can force the Visual Studio Code Java debugger to use Java 11 to run/debug the application.

Start by tracing how the Java debugger selects its launch runtime and how java.configuration.runtimes relates to the Maven POM's java-version. The work is complete when a launch configuration can explicitly select a configured Java environment, overriding the project's declared version for run and debug.