feat(click): add --js-click flag for DOM-level element.click()

[Hyeong-soo]

Problem

`click` uses CDP `Input.dispatchMouseEvent` which dispatches coordinate-based mouse events. This silently fails when:

• `pointer-events: none` — coordinates pass through to underlying elements (e.g., vercel.com navigation links)
• Viewport-obscured elements — `getBoundingClientRect()` returns incorrect coordinates for elements outside the visible area

The command reports success, but the intended element is not actually clicked. Related: #1011, #1044.

Note: SPA router click issues observed in v0.22.x appear to be resolved in v0.23.0. This PR addresses the remaining cases where coordinate-based clicking is fundamentally insufficient.

Root Cause

`Input.dispatchMouseEvent` operates at the browser input pipeline level (coordinates → hit-test → element). CSS properties like `pointer-events: none` cause the hit-test to resolve to a different element than intended, and viewport-obscured elements produce unreliable coordinates.

`element.click()` (DOM API) bypasses the coordinate system entirely and invokes the element's click handler directly, which is immune to CSS pointer restrictions and viewport position.

Changes

• `cli/src/native/interaction.rs`: Added `pub async fn js_click()` — calls `element.scrollIntoView()` + `element.click()` via `Runtime.callFunctionOn`. Mirrors the existing `js_click_checkbox()` fallback (used by `check()`/`uncheck()`), generalized for any clickable element.
• `cli/src/native/actions.rs`: `handle_click()` reads `jsClick` flag, dispatches to `js_click()` when set.
• `cli/src/commands.rs`: Parses `--js-click` CLI flag into `{ "jsClick": true }` JSON field, following the `--new-tab` pattern.

Behavior

Site	Issue	`click @ref`	`click @ref --js-click`
vercel.com	`pointer-events: none`	❌ silent fail	✅ navigates
namu.wiki	virtual rendering	❌ (element at wrong coords)	✅ navigates
example.com	(none)	✅ works	✅ works

Testing

```bash
cargo test --manifest-path cli/Cargo.toml # 542 passed, 0 failed
cargo fmt --manifest-path cli/Cargo.toml -- --check

Manual verification (pointer-events: none):

agent-browser open https://vercel.com
agent-browser snapshot -i
agent-browser click @e91 # Docs link — URL unchanged
agent-browser click @e91 --js-click # URL → /docs ✅
```

[vercel]

@Hyeong-soo is attempting to deploy a commit to the Vercel Labs Team on Vercel.

A member of the Team first needs to authorize it.