fix(cli): route JavaScript applications from analyze

[N0zoM1z0]

Summary

• route generic rea analyze calls for directories and .asar paths to the static JavaScript application provider
• keep native files, .app bundles, and explicit --provider / --snapshot requests on the existing deep-analysis path
• share the JavaScript CLI execution boundary and return actionable approval validation details
• document the generic route and verify it in source and packaged CLI tests

Root cause

The generic analyze command was hard-wired to binary_overview, so JavaScript application directories and ASARs reached native deep-provider discovery even though REA already exposed a static JavaScript application service and dedicated CLI command.

Behavior change

rea analyze PATH --approved now detects directories and .asar files and invokes analyze_javascript_application when no provider or snapshot override is present. The request still requires an administrator-approved investigation root and per-call approval.

Verification

• npm run check — 343 test files, 2,296 tests passed
• focused Electron/application CLI tests — 13 tests passed
• isolated package, install, discovery, dedicated JS CLI, and generic JS routing verification passed
• git diff --check

The complete npm run verify:package reached and passed the artifact/JavaScript routing stage, then the existing interactive setup PTY produced no output and hit its 20-second timeout in this environment. The relevant packaged stages were rerun independently and passed.

Real Hopper verification: not performed (provider adapter unchanged).
Real Ghidra verification: not performed (provider adapter unchanged).

[N0zoM1z0]

LGTM!