test(e2e): add Phase C plans — project create, export jar, delete permanently

[wenytang-ms]

Phase C of the E2E test-plan coverage push, building on PRs #1027 and #1028.

What this PR adds

Three new YAML plans under \ est/e2e-plans/\ that cover the remaining high-value Java Manager commands not yet exercised by Phase A (lifecycle / new types / file ops / view modes / project explorer) or Phase B (referenced libraries):

Plan	Command(s)	Steps
\java-dep-project-creation.yaml\	\java.project.create\	15
\java-dep-export-jar.yaml\	\java.view.package.exportJar\	14
\java-dep-delete-permanent.yaml\	\java.view.package.deleteFilePermanently\	16

After this PR, ~85% of the extension's contributed commands are covered by deterministic E2E plans. The remaining uncovered surface is either trivial (\copyFilePath\ / \copyRelativeFilePath\ — clipboard ops needing autotest helper extension) or out of scope (
evealFileInOS\ — no in-VS-Code state to assert).

Design notes

• *\project.create* uses the No build tools branch (the only project type whose scaffolding lives entirely inside this repo at \ emplates/invisible-project/\ — Maven / Gradle / Spring / Quarkus all delegate to third-party extensions). Asserts on-disk presence of scaffolded files; the \�scode.openFolder\ second-window spawn is intentionally not interacted with (Playwright is attached to the original window's renderer, the new window is a separate Electron process).
• *\�xportJar* pins \java.project.exportJar.targetPath\ via user-level \settings:\ so the wizard's \showSaveDialog\ branch is skipped (GenerateJarExecutor.ts:36-46 short-circuits only when \outputPath === ""). User-level was chosen over workspace-level because autotest's \workspaceSettings:\ merge uses \JSON.parse\ on the existing .vscode/settings.json, and the maven fixture's settings file contains JSONC comments.
• *\deleteFilePermanently* has no plain-click UI affordance for normal local files (the context-menu entry and \delete\ keybinding are both gated on !explorerResourceMoveableToTrash\ — see package.json:489 and package.json:812-820). Invocation is therefore by command id with tree-selection fallback, the same pattern
  emoveLibrary\ uses in the classpath plan.

Verification

Locally green:

\
✅ Auto-refresh targeted (#914): 16/16
✅ Build Lifecycle: 26/26
✅ Classpath / Referenced Libraries: 33/33
✅ Permanent Delete (NEW): 16/16
✅ Export Jar (NEW): 14/14
✅ File Operations: 41/41
✅ New File Types: 75/75
✅ Create Project (NEW): 15/15
✅ Project Explorer: 21/21
✅ Refresh Generated Files (#914): 21/21
✅ View Modes & Refresh: 30/30

Total: 11 plans / 308 steps — 0 failures, 0 crashes
\\

CI auto-discovers plans via the \discover-plans\ matrix in .github/workflows/e2eUI.yml, so no workflow changes are required.