fix(type): add --enter to commit async-autocomplete/tag widgets

[leeguooooo]

Problem

When automating juejin.cn's article-publish modal, the 「添加标签」(add-tag) input can't be driven. It's a framework-controlled autocomplete: a bulk Input.insertText never fires the keydown/input events the widget queries its suggestion dropdown off, so no candidate ever appears and no tag can be added — and juejin requires ≥1 tag, so publish is blocked. (In the same modal, click for the category radios and fill for title/summary work fine; only this custom widget is unreachable.)

See #50 for the full repro.

Fix

Add type --enter (alias --commit-enter):

• It implies --key-events — real per-character keystrokes, which do trigger the dropdown (a bulk insertText doesn't, so there'd be nothing for Enter to commit).
• After typing, it waits for the page to settle (RAF + microtask) so the candidate is mounted/highlighted, then presses Enter once, which these widgets read as "accept the current candidate".
• Works on both the selector path (type @e6 "ChatGPT" --enter) and the --focused path.

chrome-use type @e6 "ChatGPT" --enter   # types real keystrokes, then commits the candidate

If you'd rather pick from the list explicitly, the existing flow still works: type --key-events, then snapshot -i and click the candidate.

Changes

• cli/src/commands.rs — parse --enter/--commit-enter, force keyEvents on, thread commitEnter through; updated usage string; added test_type_commit_enter.
• cli/src/native/actions.rs — call commit_with_enter after typing when set (selector + focused paths); return committed in the result.
• cli/src/native/interaction.rs — commit_with_enter helper (settle → Enter → settle).
• skill-data/core/SKILL.md — document type --enter.

Test

cargo test test_type_commit_enter passes; full crate compiles.

Caveat: unit-tested the parser wiring; the Enter-commit event path was not live-tested against juejin from CI (no browser there). The event sequence mirrors the existing --key-events path plus a settled Enter.

Fixes #50