fix(webkit): stabilize inspector connections and disconnected states

[DjDeveloperr]

Summary

• Keep WebKit inspector attachments alive by using a more reliable socket discovery path and the missing page-activation handshake before socket setup.
• Surface daemon/provider disconnects as a stable Not connected state in the accessibility and devtools panels instead of flickering load/error states.
• Block Chrome DevTools in Safari with a clear message and stop advertising app inspectors as CDP targets.
• Patch WebInspectorUI compatibility gaps for the browser-hosted inspector so it renders consistently without spurious frontend errors.

Testing

• cargo test --manifest-path server/Cargo.toml webkit
• cargo clippy --manifest-path server/Cargo.toml --all-targets -- -D warnings
• npm run build:cli
• npm run build:client
• Playwright E2E on http://127.0.0.1:4310/: opened WebKit DevTools for Safari, confirmed DOM protocol completion and a stable inspector WebSocket over a 60s hold, and verified the panel did not fall back to reconnecting/loading states.