Set environment variables for language server

As far as I understand this extension launches the process for the language server backend. It could be beneficial to be able to configure the environment variables used when executing the language server, in a similar fashion as in the 'Maven for Java' extension here: https://github.com/Microsoft/vscode-maven/#additional-configurations

My use case is the following:

I am using VS Code with Remote SSH, and trying to work on a Maven based Java project. Currently I am configuring the java.configuration.maven.userSettings setting to point to a project specific Maven settings file. This settings file makes use of an environment variable, which is not set by default on the remote machine shell as it changes from project to project. Therefore the extension imports and tries to build this Maven project, the user settings is used correctly, but the environment variable is not defined.

(Sorry if this suggestion is incorrect, as I am a new user of the extension)

Environment

• Operating System: Linux
• JDK version: 11
• Visual Studio Code version: 1.65.0
• Java extension version: 1.4.0

Steps To Reproduce

1. Use VS Code Remote SSH on a machine that does NOT have the environment variable MY_REPO defined by default.
2. Create Maven settings file with: <localRepository>${MY_REPO}/repo</localRepository>
3. Set java.configuration.maven.userSettings to point to the created Maven settings file
4. Create Maven Java project and let the extension import and build the project

A local folder called "${MY_REPO}" will be created, as the environment variable is not defined.

Current Result

Environment variable used in Maven settings file cannot be configured.

Expected Result

Environment variable used in Maven settings file can be configured.

Es werden keine Quelldateien oder Tests genannt. Beginne damit nachzuverfolgen, wie die Erweiterung das language-server-Backend startet und wie java.configuration.maven.userSettings Maven erreicht; reproduziere das mit Remote SSH und MY_REPO, wobei die Arbeit erfolgt, wenn die konfigurierte Umgebungsvariable während des Projektimports und des Builds verfügbar ist.