Browserbase integration broken: static cdpUrl no longer works (404)

Description

The OpenClaw browser docs recommend this config for Browserbase:

"browserbase": {
  "cdpUrl": "wss://connect.browserbase.com?apiKey=<API_KEY>",
  "color": "#F97316"
}

The docs state: "Browserbase auto-creates a browser session on WebSocket connect, so no manual session creation step is needed."

This no longer works. Browserbase has changed their API — wss://connect.browserbase.com?apiKey=... now returns HTTP 404. They require:

1. POST https://api.browserbase.com/v1/sessions → returns ephemeral connectUrl
2. Connect to connectUrl (e.g. wss://connect.usw2.browserbase.com/?signingKey=...)

Steps to Reproduce

1. Sign up on browserbase.com, get API key
2. Configure browser profile with cdpUrl: "wss://connect.browserbase.com?apiKey=<KEY>"
3. Try browser open url=https://example.com profile=browserbase
4. Error: "Remote CDP websocket for profile 'browserbase' is not reachable"

Expected Behavior

OpenClaw should handle Browserbase session lifecycle automatically — create session via REST API before connecting CDP WebSocket.

Proposed Solution

Add Browserbase-aware logic to the browser profile connection:

• Detect cdpUrl containing browserbase.com
• Auto-create session via POST /v1/sessions using API key from URL
• Connect to returned connectUrl
• Auto-close session when browser tab/profile is released

Alternatively, support env vars BROWSERBASE_API_KEY and BROWSERBASE_PROJECT_ID for session management.

Environment

• OpenClaw 2026.3.8
• Browserbase Free tier
• Server: Ubuntu 24.04 (Kazakhstan IP)

Workaround

Manual workflow: create session via curl, update cdpUrl in config, use config.patch to hot-reload.