#2174: store VSCode user-data under $IDE_HOME/.ide/vscode/<workspace>/config

[quando632]

This PR fixes #2174 (part of #2142)

Moves VSCode user-data out of the workspace into the dedicated $IDE_HOME/.ide/vscode/«workspace»/config folder so workspaces stay clean and independent of the IDE.

Stacked on #2175 (#2172 – getIdeMetadataPath()); its commits appear here until #2175 is merged, then this branch is rebased onto main.

Implemented changes:

• Vscode.configureToolArgs now points --user-data-dir to getIdeMetadataPath().resolve("config") instead of «workspace»/.vscode/.userdata. The folder VSCode opens (getWorkspacePath()) is unchanged.
• Migration Mig202608001 (target 2026.08.001) moves any existing .vscode/.userdata of every workspace to the new location. It is idempotent: skips workspaces already migrated and skips (with a warning, no overwrite) if a target already exists. Registered in IdeMigrator.
• Tests: VscodeTest.testConfigureToolArgsUsesIdeMetadataPathForUserData, Mig202608001Test (move, no-op, and target-exists cases).

Testing instructions

1. cd cli && mvn -Dtest=VscodeTest,Mig202608001Test,IdeMigratorTest test — all pass.
2. Manual: create $IDE_HOME/workspaces/main/.vscode/.userdata/state.json, run ide update, verify it moved to $IDE_HOME/.ide/vscode/main/config/state.json and the workspace no longer contains .vscode/.userdata.

---

Checklist for this PR

• When running mvn clean test locally all tests pass and build is successful (ran the affected tests)
• PR title is of the form #«issue-id»: «brief summary»
• 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
• You followed all coding conventions
• You have added the issue implemented by your PR in CHANGELOG.adoc (added under Move IDE-specific metada (.idea, .vscode) out of workspace #2142 in #2172: add getIdeMetadataPath() for $IDE_HOME/.ide/<ide>/<workspace> #2175)
• You have formulated clear instructions on how to test your contribution under "Testing instructions"

Coordination note

IdeMigrator requires strictly ascending migration versions. The JetBrains subtask (#2173) also adds a migration — whichever merges second must adjust its version to stay ascending.

[coveralls]

Coverage Report for CI Build 30438912015

Coverage increased (+0.03%) to 72.626%

Details

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

Uncovered Changes

No uncovered changes found.

Coverage Regressions

9 previously-covered lines in 2 files lost coverage.

File	Lines Losing Coverage	Coverage
com/devonfw/tools/ide/tool/ide/IdeToolCommandlet.java	6	81.97%
com/devonfw/tools/ide/migration/IdeMigrator.java	3	89.83%

---

Coverage Stats

Relevant Lines:	17018
Covered Lines:	12886
Line Coverage:	75.72%
Relevant Branches:	7611
Covered Branches:	5001
Branch Coverage:	65.71%
Branches in Coverage %:	Yes
Coverage Strength:	3.21 hits per line

---

💛 - Coveralls

[quando632]

Update: the JetBrains PR #2208 no longer adds a migration (the vmoptions cleanup migration was dropped as unnecessary — vmoptions regenerate at the new location). So there is no migration-version coordination needed anymore; this PR's Mig202608001 stands alone.

[QuangAnhLe]

Core implementation is correct and well-tested. Merge-ready after rebase

[QuangAnhLe]

@quando632 and @hohwille : Should PyCharm, AndroidStudio, and Eclipse Move Metadata Like VSCode?

[quando632]

We decided not to move the .idea folder because IntelliJ already excludes .idea from its own search/indexing, .idea is effectively the project definition. Relocating it would be only possible via symlink and that would add risk for a little benefit