#1676: import extra sdks automatically into ide

[JoelAdbu]

This PR fixes #1676

• this pr is a follow-up to PR: #1676 import extra sdks automatically into ide  #2073

Implemented changes:

1. Register the IntelliJ template

• Add the IntelliJ template for extra JDKs installations.
• Keep the approach reusable for other IDEs, such as Eclipse and VS Code.

2. Read extra tool installations

• Read extra tool installations from $IDE_HOME/settings/ide-extra-tools.json.
  For example:

{
  "java": {
    "client": {
      "version": "11.0.31_11",
	   "edition": "azul"
    },
    "process-engine": {
      "version": "21.*"
    }
  },
  "mvn": {
    "m4": {
      "version": "4.0.0-rc-5"
    }
  }
}

• Process each configured extra SDKs installation.

3. Keep SDKs synchronized

• Synchronize extra SDKs during ide create or ide update and before the IDE starts.
• Configure the workspace only after tools are installed.
• Use merge logic to update SDKs without duplicates (Related PR devonfw/IDEasy#1676: import extra sdks automatically into ide (new) ide-settings#91).

4. Validate configuration and handle errors

• Reject an extra-installation name that equals its tool name; for example, an extra JDKs installation must not be named java.
• Skip missing or invalid SDK installations and write a warning to the log.

5. Added GraalVM reflection metadata to reflect-config.json

• The new entries enable native-image to instantiate Intellij via IdeToolCommandlet-based lookup.

---

Testing instructions

1. Build the native executable

• Run the following script to build the native image: ./build-local-dev.sh.
• After the build completes, navigate to: IDEasy/cli/target.

2. Create a test project with custom settings

• From IDEasy/cli/target, create a new test project using the modified settings from my test branch for ide-settings.

ideasy.exe create <test-import-sdks> https://github.com/vivu001/ide-settings.git#feature/1676-Test-import-extra-SDKs-automatically-into-IDE

3. Verify automatic SDK import in IntelliJ

• Open a new terminal and initialize the workspace:

icd -p <test-import-sdks> -w

• Launch IntelliJ

ide intellij

• Expected result:
  All additional SDKs should be automatically imported into IntelliJ.
  This step validates that workspace configuration and IDE settings are correctly applied (as IDEasy manages IDE configuration via workspace templates).

4. Validate ide update behavior

4.1 Prepare test scenario

• Manually remove all extra JDKs from IntelliJ.
• Additionally, delete jdks from the filesystem:

$IDE_HOME/software/java 
$IDE_ROOT/_ide/software/default/java

4.2 Run update

ide update

4.3 Verify result

All previously removed SDKs are re-downloaded and reinstalled.
IntelliJ configuration is updated accordingly, as shown at the end of step 3.
The file $IDE_HOME/workspaces/main/.intellij/config/options/jdk.table.xml has been updated with the extra SDK entries.

Checklist for this PR

Make sure everything is checked before merging this PR. For further info please also see
our DoD.

• When running mvn clean test locally all tests pass and build is successful
• PR title is of the form #«issue-id»: «brief summary» (e.g. #921: fixed setup.bat). If no issue ID exists, title only.
• PR top-level comment summarizes what has been done and contains link to addressed issue(s)
• PR and issue(s) have suitable labels
• Issue is set to In Progress and assigned to you or there is no issue (might happen for very small PRs)
• You followed all coding conventions
• You have added the issue implemented by your PR in CHANGELOG.adoc unless issue is labeled
  with internal
• You have formulated clear instructions on how to test your contribution under "Testing instructions"

[coveralls]

Coverage Report for CI Build 32485106491

Coverage increased (+0.1%) to 73.677%

Details

• Coverage increased (+0.1%) from the base build.
• Patch coverage: No coverable lines changed in this PR.
• 49 coverage regressions across 6 files.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

49 previously-covered lines in 6 files lost coverage.

File	Lines Losing Coverage	Coverage
com/devonfw/tools/ide/context/IdeContext.java	16	77.46%
com/devonfw/tools/ide/git/repository/RepositoryCommandlet.java	12	73.43%
com/devonfw/tools/ide/tool/ide/IdeToolCommandlet.java	9	88.32%
com/devonfw/tools/ide/commandlet/AbstractUpdateCommandlet.java	7	82.2%
com/devonfw/tools/ide/tool/intellij/Intellij.java	4	89.41%
com/devonfw/tools/ide/tool/extra/ExtraTools.java	1	90.48%

---

Coverage Stats

Relevant Lines:	17840
Covered Lines:	13746
Line Coverage:	77.05%
Relevant Branches:	7909
Covered Branches:	5225
Branch Coverage:	66.06%
Branches in Coverage %:	Yes
Coverage Strength:	3.28 hits per line

---

💛 - Coveralls

[hohwille]

@JoelAdbu thanks for taking over and bringing this to the finishing line. Great job 👍
For me everything looks perfect for merge but I have one last question because we should not use reflection to fiddle with out commandlets.