chore: sync upstream + 0.2.1 patch

[triuzzi]

Summary

• Sync fork with upstream ChromeDevTools/chrome-devtools-mcp (10 new commits rebased below our Brave commits)
• Rebrand docs/cli.md for Brave (was still entirely Chrome-branded — missed in the initial port)
• Fix src/version.ts drift (was hardcoded at 0.1.0 while package was 0.2.0, causing the CLI to report the wrong version and nag local builds with a false update prompt) by bumping it alongside package.json to 0.2.1

Upstream commits pulled in

• 0331f6a chore: implement memory snapshot information (chore: implement memory snapshot information ChromeDevTools/chrome-devtools-mcp#1874)
• ea57e86 fix: ignore unmapped PerformanceIssue events (fix: ignore unmapped PerformanceIssue events ChromeDevTools/chrome-devtools-mcp#1852)
• 2f458c1 fix(network): trailing data in Network redirect chain (fix(network): trailing data in Network redirect chain ChromeDevTools/chrome-devtools-mcp#1880)
• 49f46b3 chore: amend security guidelines (chore: amend security guidelines ChromeDevTools/chrome-devtools-mcp#1890)
• 3f0cf10 fix: avoid showing update notification for local builds (fix: avoid showing update notification for local builds ChromeDevTools/chrome-devtools-mcp#1889) — added semver dep
• 796d6f2 docs: document network response and request extensions (docs: document network response and request extensions ChromeDevTools/chrome-devtools-mcp#1887)
• 54cfc7e chore(deps-dev): bump protobufjs 7.5.4 → 7.5.5 (chore(deps-dev): bump protobufjs from 7.5.4 to 7.5.5 ChromeDevTools/chrome-devtools-mcp#1885)
• e102a43 test: try things to reduce flakiness (test: try things to reduce flakiness ChromeDevTools/chrome-devtools-mcp#1879)
• 6ba1816 test: add debug logs when running GitHub actions in debug (test: add debug logs when running GitHub actions in debug ChromeDevTools/chrome-devtools-mcp#1878)
• 0287486 chore: minor fixes to build and evals (chore: minor fixes to build and evals ChromeDevTools/chrome-devtools-mcp#1875)

Note: the three existing Brave commits (port, README rebrand, 0.2.0) are included in this PR with new SHAs because they were rebased onto the new upstream. Merge with rebase to keep a clean linear history.

Verified

• --usage-statistics still defaults to false
• Bins still brave-mcp / brave-devtools-mcp / brave-devtools
• tsc passes
• CLI smoke test on Brave: start, status, list_pages, navigate_page url --url, evaluate_script, take_screenshot, list_console_messages, list_network_requests, --output-format=json, stop
• MCP smoke test (first 10 tools of tests/e2e/brave-integration.test.mjs) passes against live Brave — further tests OOM'd due to event volume from the user's real browser, not a regression

Test plan

• CI green
• After merge, tag v0.2.1 and create GitHub pre-release