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.

extensions/ab-connect/NOTICE.md

@@ -4,8 +4,8 @@ The chrome.debugger attach + CDP Target handling in `background.js` is adapted
 from **openclaw-browser-relay** by chengyixu
 (https://github.com/chengyixu/openclaw-browser-relay, MIT per its README).
 
-Changes for agent-browser-stealth: rebranded to "agent-browser connect"; the
+Changes for chrome-use: rebranded to "chrome-use connect"; the
 transport is rewritten from a localhost WebSocket + shared token to Chrome
-**native messaging** (host `com.agent_browser.connect`) — no port, no token,
+**native messaging** (host `com.leeguoo.chrome_use`) — no port, no token,
 Chrome authenticates the extension to the host by id. WebSocket/token/options
 code removed.