Drop browser-process gate to support Edge and any Chromium browser (Closes #55)

[gkd2323c]

Background

Issue #55 reports that browser-mode commands (bilibili / zhihu / twitter / etc.) refuse to work on Microsoft Edge, because is_chrome_running() only checks for chrome.exe and never recognizes msedge.exe. autocli doctor shows the extension is connected, yet commands still fail with "Chrome is not running". A second, related bug: even after the gate is gone, wake_chrome() hardcodes launching Google Chrome, so on a machine without/avoiding Chrome the daemon would still spawn Chrome when the extension needs waking.

Changes in this PR

1. Remove the browser-process detection gate

• Deletes is_chrome_running() and its call site in connect_daemon_page
• The connection flow proceeds straight to the daemon handshake; whether a browser is usable is decided by the real daemon↔extension connection state, not by a guessed process name

2. Make wake_chrome() open the default browser, not Chrome

• Windows: cmd /C start "" about:blank (empty title arg so about:blank is treated as a URL, not a program name)
• macOS / Linux: open / xdg-open about:blank
• No browser binary is hardcoded, so Edge/Brave/Arc/etc. are all woken correctly

Why this beats the allowlist approach

The original issue proposed adding msedge.exe (and macOS/Linux equivalents) inside is_chrome_running(). Removing the gate is more fundamental:

• Universal: any Chromium browser with the extension installed (Chrome / Edge / Brave / Arc / Vivaldi / etc.) works out of the box, with no per-browser allowlist
• Honest: when the extension is not connected it reports Chrome extension not connected instead of masquerading as Chrome is not running
• Zero maintenance: no need to grow the process-name list as new browsers appear

Verification

• cargo build --release passes
• autocli doctor shows Chrome extension connected with only Edge running (no Chrome)
• Browser-mode commands such as autocli zhihu hot fetch data end-to-end
• Forced the wake path (restarted daemon to drop the extension connection): confirmed no chrome.exe process is spawned; the default browser (Edge) is used instead
• Existing pure-API public commands (hackernews, etc.) are unaffected

Only crates/autocli-browser/src/bridge.rs is changed (two commits: gate removal + wake fix).

Closes #55