HAPI Chat 0.5.2: fix queued messages across multiple websites

Fix persistent Queued messages and disabled queue controls when many websites from one HAPI hub are open.

Native HAPI websites keep two long-lived event streams. A shared HTTP/1 loopback origin could exhaust Chromium's six connection slots, leaving message POSTs waiting before reaching the hub. Each open website instance now has an independent loopback origin, including retained sidebar chats and duplicate native panels. Saved tokens still sign in automatically, and closing a page releases its adapter without stopping the agent.

Keeps per-hub Proxy settings and HAPI Chat tab icons from 0.5.1.

Validated with 28 tests, a headless browser with ten retained website frames and eight successful browser message POSTs, and real VS Code host checks with two persistent streams per mock website. The real Persona hub was checked read-only. No real agent sessions were created or restarted.

After installation, run Developer: Reload Window to load the fix. Browser requests that were still blocked locally may need to be sent again after checking conversation history. The extension never automatically replays messages with an uncertain outcome.