Resolves the merge conflict with master after warpdotdev#9667 (Mistral Vibe agent
recognition) merged. Combines both surfaces:

- The Vibe arm now also resolves through path_basename_token and
  shebang_script_basename, so `/usr/local/bin/vibe-acp` and
  `node /opt/vibe-acp` both detect as Vibe.

Also addresses oz-for-oss review on PR warpdotdev#10022:

> This treats the first non-flag token as a script even when the
> preceding runtime flag consumes an argument, so invocations like
> `node -e codex`, `node --require codex`, or `python -c claude` can
> false-positive as agents.

Adds VALUE_TAKING_RUNTIME_FLAGS, a list of flags that consume the
following token as their value:
- Node: -e, --eval, -p, --print, -r, --require, -C, --conditions
- Python: -c, -m, -X, -W
- Deno (subset): -A, --allow-read, --allow-write, --allow-net
- Bun (subset): -d, --define

shebang_script_basename now consumes the value alongside the flag, so
`node -e codex` no longer false-positives as Codex. The `--key=value`
form remains a single whitespace token and is handled by the existing
`starts_with('-')` flag check.

New regression tests in cli_agent_tests.rs:
- `node -e codex` → None
- `node --eval codex` → None
- `node --require claude /home/user/app.js` → None
- `python -c claude` → None
- `python -m gemini` → None
- `node --require some-mod /usr/local/bin/codex` → Codex (legitimate
  agent script after value-taking flag is consumed)
- `node --inspect=127.0.0.1:9229 /usr/local/bin/codex` → Codex
  (--key=value form preserves correct script detection)

…tdev#9667)

## Description

Resolves warpdotdev#9607. Adds `CLIAgent::Vibe` so running `vibe` (or `vibe-acp`)
in a Warp pane is detected as a known CLI agent on par with Claude Code,
Codex, Gemini CLI, OpenCode, etc. Mistral Vibe is the open-source
ACP-compatible CLI shipped alongside Devstral 2.

The change is purely additive and follows the existing `CLIAgent`
pattern in `app/src/terminal/cli_agent.rs`:

| Property | Value |
|---|---|
| `command_prefix` | `"vibe"` |
| `display_name` | `"Mistral Vibe"` |
| `brand_color` | Mistral orange `#FA520F` (new `MISTRAL_ORANGE`
constant) |
| `brand_icon_color` | white (default arm) |
| `supported_skill_providers` | `&[SkillProvider::Agents]` |
| `icon` | `None` — see below |

Telemetry: `CLIAgentType::Vibe` added in lockstep so `From<CLIAgent> for
CLIAgentType` stays exhaustive.

### Why `icon()` returns `None`

Shipping `Icon::MistralLogo` requires an officially licensed SVG that I
don't have rights to bundle. The brand-color tile still renders, and the
agent is fully detected. A follow-up PR can wire the `Icon::MistralLogo`
variant + asset once the Warp team / Mistral provide one — the issue
author explicitly suggested this draft-PR approach.

## Linked Issue

- [x] The linked issue is labeled `ready-to-spec` or
`ready-to-implement`. (warpdotdev#9607 is `ready-to-implement`.)

Resolves warpdotdev#9607.

## Testing

Extended the existing `test_detect_known_agents` table-driven test to
cover `vibe` -> `CLIAgent::Vibe`. The pre-existing
`test_serialized_name_round_trips_known_agents` exercises every variant
via `enum_iterator::all`, so it now also covers Vibe's serde round-trip
without code changes.

Local builds blocked on missing Xcode `metal` compiler in this
environment; CI's MacOS / Linux / Windows lanes will validate `cargo
build`, `cargo clippy --workspace --all-targets --all-features --tests
-- -D warnings`, and `cargo nextest run`.

## Agent Mode

- [ ] Warp Agent Mode - This PR was created via Warp's AI Agent Mode

<!--
CHANGELOG-IMPROVEMENT: Recognize Mistral Vibe (`vibe` / `vibe-acp`) as a
known CLI agent in the terminal, with brand-colored toolbar tile. Thanks
@lonexreb!
-->

CHANGELOG-IMPROVEMENT: Recognize Mistral Vibe (`vibe` / `vibe-acp`) as a
known CLI agent in the terminal, with brand-colored toolbar tile. Thanks
@lonexreb!