Bug Description:
When connecting to /chrome endpoint, the debugger frontend incorrectly prepends /chrome to all subsequent API calls, causing 404 errors for management endpoints.

Steps to Reproduce:

1. Use Chrome image with debugger URL: wss://domain.com/chrome
2. Debugger opens successfully
3. Debugger attempts to call /chrome/sessions and /chrome/devtools (both return 404)

Expected Behavior:

• Initial connection: wss://domain.com/chrome ✅
• Sessions endpoint: GET /sessions ✅
• DevTools endpoint: GET /devtools ✅

Actual Behavior:

• Initial connection: wss://domain.com/chrome ✅
• Sessions endpoint: GET /chrome/sessions ❌ (404)
• DevTools endpoint: GET /chrome/devtools ❌ (404)

Root Cause:
The debugger frontend is using the initial WebSocket connection path (/chrome) as a base path for all HTTP API calls, but management endpoints like /sessions and /devtools are browser-agnostic and should not have browser-specific prefixes.

Workaround:
Enable root path / for websockets instead of /chrome, but this forces Chromium instead of Chrome browser.