feat: add native source-map-parser CLI (crates/cli)

[MasonChow]

Motivation

• Provide a native single-file CLI so callers can map minified JS stacks without Node/WASM or npm dependencies.
• Expose the three primary library operations (map / lookup / unpack) as subcommands so behavior aligns with the Rust API surface.
• Replace the existing template-based resolver with a safe --map-url-template string replacement (no eval/JS execution) and add an option to disable network fetches.

Description

• Add a new workspace member crates/cli implementing a source-map-parser [[bin]] with map, lookup, and unpack subcommands and global --output/--pretty/--quiet flags.
• Implement map semantics with mutually-exclusive --map / --map-dir / --map-url-template, per-frame context (--context), --no-fetch, JSON output shaped as { success: [...], fail: [...] }, and exit codes per the spec.
• Reuse the existing library APIs and parsers (crates/source_map_parser and stack_transform) for mapping, token lookup (with optional context), and unpacking sources instead of reimplementing sourcemap logic.
• Update Cargo.toml to include crates/cli in the workspace and extend .github/workflows/release.yml to build the native binary on the existing platform matrix and stage/upload source-map-parser-<platform>-<arch> artifacts with checksums; also adjust a few lifetime signatures in stack_transform to silence warnings.

Testing

• Ran cargo check --workspace --exclude source_map_parser_node and it completed successfully.
• Ran cargo test --workspace --exclude source_map_parser_node --all-features and all unit and integration tests passed.
• Verified the CLI entrypoints with cargo run -q -p source-map-parser-cli -- --help and cargo run -q -p source-map-parser-cli -- map --help, which produced the expected help and usage text.
• Local build/format/check cycles (cargo fmt, cargo check, cargo build during CI changes) completed without errors.

---

Codex Task