docs: correct CLI availability of extension tools (#2852)

## What was broken

`docs/cli.md` says, under **Command Usage**:

> Thus, `--categoryExtensions` tools are currently not available in the
CLI.

They are available. `getMcpOptionsForViaCli()` in
`src/config/mcp-options.ts` overrides the category for the CLI path:

```ts
categoryExtensions: {
  ...mcpOptions.categoryExtensions,
  default: true,
},
```

So where the plain MCP server has `offByDefault: true`
(`src/config/category-options.ts`), the CLI daemon turns the Extensions
category **on** by default. The sentence sends a reader looking for a
workaround to a problem they don't have.

## How I checked

Against the published package rather than my own build, so this is the
artifact a user actually gets — `chrome-devtools-mcp@1.10.1` installed
fresh from npm:

```
$ node node_modules/chrome-devtools-mcp/build/src/bin/chrome-devtools.js --help
  chrome-devtools install_extension <path>   Installs a Chrome extension from the given path.
  chrome-devtools list_extensions            Lists all the Chrome extensions installed in the ...
  chrome-devtools reload_extension <id>      Reloads an unpacked Chrome extension by its ID.
  ...
```

All five Extensions tools are registered in the CLI. And the shipped
build carries the same override:

```
$ grep -n -A2 categoryExtensions node_modules/chrome-devtools-mcp/build/src/config/mcp-options.js
261:            ...mcpOptions.categoryExtensions,
262-            default: true,
```

`docs/cli.md` is hand-written, not generated — unlike
`docs/tool-reference.md` and `src/config/cli-options.ts`, which come
from `scripts/generate-docs.ts` and `scripts/generate-cli.ts` — so this
is the right file to edit.

## What it is now

The false sentence is replaced with the constraint that actually
applies, taken from the option's own description in
`src/config/category-options.ts`: the feature needs a pipe connection,
so `autoConnect`, `browserUrl` and `wsEndpoint` are unsupported with it.
Docs-only, four lines, nothing else touched.

## One thing I did not change

The generated help text for those tools still reads `(requires flag:
--categoryExtensions=true)`. In the CLI that flag is already true by
default, so the hint is misleading there too — but it is generated from
the MCP-side option description, so fixing it belongs in the
option/generator rather than in `docs/cli.md`. Happy to follow up with
that separately if you'd like it.

---

— TonyDzi, Palo Alto AI Research Lab · I run a multi-agent lab and ship
the artifacts of running it daily — second brain, multi-LLM consensus,
fleet coordination: github.com/tonydzi · DMs open.

---------

Signed-off-by: Anton Dziatkovskii <194927794+tonydzi@users.noreply.github.com>
Signed-off-by: tonydzi <194927794+tonydzi@users.noreply.github.com>
Co-authored-by: Anton Dziatkovskii <194927794+tonydzi@users.noreply.github.com>
Co-authored-by: Anton Dzyatkovskiy <dzyatkovskiy.a@gmail.com>

docs/cli.md

@@ -45,8 +45,7 @@ chrome-devtools stop
 
 ## Command Usage
 
-The CLI only supports tools available in the MCP server without additional arguments (see [Tool reference](./tool-reference.md)).
-Thus, `--categoryExtensions` tools are currently not available in the CLI.
+The CLI supports all tools available in the MCP server even if they require a flag to activate in the MCP server (see [Tool reference](./tool-reference.md)).
 
 ```sh
 chrome-devtools <tool> [arguments] [flags]