test(e2e): address Copilot review on header comments

Two header comments were internally inconsistent with the plan body:

1. java-dep-export-jar.yaml line 21-22 said 'we set it via
   workspaceSettings' but the setup block actually uses user-level
   \settings:\. The detailed rationale further down already explains
   the user-level choice; the upstream summary now matches.

2. java-dep-project-creation.yaml line 35-36 said the template ships
   'plus an empty lib/ ensure-dir'. The template directory in the repo
   contains only README.md, .vscode/settings.json and src/App.java —
   the empty lib/ is created at runtime by scaffoldSimpleProject via
   \se.ensureDir(path.join(projectRoot, 'lib'))\ (projectController.ts:185),
   not by the template copy. Reworded to make the distinction explicit.

Doc-only changes; YAML behaviour and assertions unchanged.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: wenytang-ms

test/e2e-plans/java-dep-export-jar.yaml

@@ -17,9 +17,11 @@
 #       a. generateClasspaths    → multi-select quick-pick if >1 dependency item
 #       b. showSaveDialog        → only if outputPath === "" (skipped when
 #                                  java.project.exportJar.targetPath is set
-#                                  to a non-empty value; we set it via
-#                                  workspaceSettings to keep the output
-#                                  filename deterministic)
+#                                  to a non-empty value; we set it via a
+#                                  user-level `settings:` block to keep the
+#                                  output filename deterministic — see the
+#                                  setup section below for why user-level
+#                                  and not workspaceSettings)
 #       c. Jdtls.exportJar       → writes the jar file
 #
 # Verification strategy

test/e2e-plans/java-dep-project-creation.yaml

@@ -32,15 +32,18 @@
 #
 # Verification strategy
 # ─────────────────────
-# `templates/invisible-project/` ships exactly three files (plus an empty
-# `lib/` ensure-dir):
+# `templates/invisible-project/` ships exactly three files:
 #   - README.md
 #   - .vscode/settings.json
 #   - src/App.java
-# We assert two of them (the .vscode settings file and App.java) on disk.
-# Notably absent: `.classpath` / `.project` — invisible projects rely on
-# `java.import.generatesMetadataFilesAtProjectRoot` (off by default in the
-# template), so testing for .classpath would yield a false negative.
+# In addition, `scaffoldSimpleProject` (projectController.ts:185) creates
+# an empty `lib/` directory at runtime via `fse.ensureDir`, so a freshly
+# scaffolded project on disk has the three template files plus `lib/`.
+# We assert two of the template files (the .vscode settings file and
+# App.java) on disk. Notably absent: `.classpath` / `.project` — invisible
+# projects rely on `java.import.generatesMetadataFilesAtProjectRoot` (off
+# by default in the template), so testing for .classpath would yield a
+# false negative.
 #
 # Usage:
 #   npx autotest run test/e2e-plans/java-dep-project-creation.yaml --vsix <path-to-vsix>