rebrand: agent-browser-stealth → chrome-use, de-fork, reset to v1.0.0

Standalone product rename across the whole repo (issue: project identity):

- Binary/package/repo/skill/docs: agent-browser[-stealth] → chrome-use
  (single binary name `chrome-use`; old aliases agent-browser/abs dropped).
- Version: 0.27.0-fork.51 → 1.0.0 (drop the upstream-fork counter).
- Native-messaging host: com.agent_browser.connect → com.leeguoo.chrome_use
  (CLI + ab-connect extension in lockstep — this is a breaking handshake change,
  extension bumped 0.4.2 → 0.5.0, needs a Web Store republish).
- Config dir: ~/.agent-browser → ~/.chrome-use.
- README/zh: reframed from "stealth fork of agent-browser" to a standalone
  product with a small `originally based on vercel-labs/agent-browser` credit.
- Kept AGENT_BROWSER_* env vars working (63 vars across the codebase; renaming
  them would break every existing script/skill for no user-facing gain).

Build green, 802 unit tests pass, fmt + clippy clean. Upstream attribution to
vercel-labs/agent-browser preserved.

cli/src/native/relay.rs

@@ -12,7 +12,7 @@
 //!
 //! ## Multiple clients (concurrent agents on one shared browser)
 //!
-//! Several agent-browser daemons (one per `--session`) can connect to the same
+//! Several chrome-use daemons (one per `--session`) can connect to the same
 //! relay/Chrome at once. The extension is a single peer, so the relay must
 //! demultiplex: every forwarded command is re-keyed to a relay-global id mapped
 //! back to the originating client, and the extension's reply is routed to **only
@@ -31,7 +31,7 @@ use serde_json::{json, Value};
 /// Protocol version advertised in the connect handshake (matches the extension).
 pub const RELAY_PROTOCOL: i64 = 3;
 
-/// Identifies one connected CDP client (agent-browser daemon) for routing.
+/// Identifies one connected CDP client (chrome-use daemon) for routing.
 pub type ClientId = u64;
 
 /// One target (tab) the extension has attached, as the relay tracks it.