Lighthouse MCP cannot reuse logged‑in Chrome sessions (no profile support)

[areibman]

The MCP server always launches a fresh Chrome instance with a temporary profile and resets storage for each audit. That makes it impossible to run Lighthouse against authenticated pages or sessions that require login. Users cannot pass a persistent Chrome profile or attach to an existing Chrome session in a supported way, so audits of private/internal routes fail or show logged‑out experiences.

• Authenticated pages are audited as anonymous users
• Protected routes return login screens or redirect
• Manual testing with logged‑in sessions is blocked

Solution:
Allow users to pass a persistent Chrome profile (or attach to an existing Chrome with remote debugging) so Lighthouse can run against authenticated sessions, with storage preserved when profile mode is enabled.

I've created a PR that addresses this: #134