fix(javascript): classify application input selection failures by cause

analyze_javascript_application reported every input-selection problem as
an artifact fault:

- a missing input path: "Artifact could not be read or written", with no
  path or reason;
- an unreadable selected directory: the same generic io failure;
- a regular file that is neither a directory nor an .asar, and a
  --artifact-format that contradicts the selection: "Artifact is invalid
  or has changed. Get a fresh copy and try again."

Report a missing path as an invalid input_path, an unreadable selection
as access_denied, a non-directory non-.asar file as unsupported_target
with the accepted inputs as remediation, and a contradicting format as an
invalid format with the observed kind as expected value. Failures inside
a selected artifact keep their existing classification.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

tests/boundary/cli/javascriptApplicationProgress.test.ts

@@ -62,7 +62,7 @@ cliTest(
         "--json",
       ],
     });
-    expect(output.json).toMatchObject({ code: "artifact_operation_failed" });
+    expect(output.json).toMatchObject({ code: "invalid_request" });
     const updates = output.stderr
       .trim()
       .split("\n")