[Feature Request] Allow to share the scanner config file between CI/CD processes and developer environments

### Need/Problem Description

As a developer, I would like to use the same scanner configuration which is used when running CI/CD processes (including same custom PMD rules) while my PMD jars containing classes required by the custom PMD rules are located in other folders than for CI/CD processes - both when using the command line as well as in Visual Studio Code.

### Describe your Desired Solution

An environment variable could be used inside the PMD classpath in code-analyzer.yml:
java_classpath_entries:
- %CUSTOM_PMD%/pmd-jars/pmd-customjar.jar

Or;
java_classpath_entries:
- %CUSTOM_PMD_JARS%

A second variable could contain the PMD rule sets to execute.

The environment variable could be set to correct values in CI/CD and for each developer machine.

While I believe that the Visual Studio Code extension does not consider the scanner configuration file (code-analyzer.yml), if that is implemented, it could consider that environment variable as well.

### Alternatives Considered

_No response_

### Additional Context (Screenshots, Files, etc)

_No response_

### Workaround

_No response_

### Urgency

Low

Beginne damit nachzuverfolgen, wie code-analyzer.yml vom command-line scanner verwendet wird und ob die Visual Studio Code extension die Datei liest. Untersuche anschließend, wie java_classpath_entries und die Auswahl der PMD rule sets aufgelöst werden. Das Ziel ist erreicht, wenn dieselbe Scanner-Konfiguration umgebungsspezifische PMD-Pfade und rule sets in CI/CD, bei der Verwendung über die command line und in Visual Studio Code nutzen kann.

Vom Indexierungsmodell aus dem Issue-Text verfasst.