fix: add dialog recovery mechanism to prevent grey screen issue

[roomote]

This PR fixes the grey screen issue reported in #6283 where the Roo Code interface becomes unresponsive with a grey overlay.

Problem

The issue occurs when dialog components (HumanRelayDialog, DeleteMessageDialog, or EditMessageDialog) get stuck in an open state without their content rendering properly, leaving only the semi-transparent grey overlay visible.

Solution

Implemented a multi-layered recovery mechanism:

1. Automatic Recovery: Added a 30-second timeout that automatically closes any stuck dialogs
2. Error Boundaries: Created DialogErrorBoundary component to catch and handle errors in dialog content
3. Manual Recovery: Added Escape key handler for users to manually close stuck dialogs
4. Telemetry: Added logging to track when dialog recovery is triggered for debugging

Changes

• Modified webview-ui/src/App.tsx to add recovery mechanisms
• Created webview-ui/src/components/ui/DialogErrorBoundary.tsx for error handling
• Wrapped all dialog components with error boundaries

Testing

• All existing tests pass ✅
• Linting and type checking pass ✅
• The recovery mechanism will activate if any dialog remains open for 30 seconds
• Users can press Escape to manually recover from stuck dialogs

Fixes #6283

---

Important

Introduces a dialog recovery mechanism in App.tsx to prevent grey screen issues by adding automatic, manual, and error boundary-based solutions.

• Behavior:
  • Adds a 30-second timeout in App.tsx to automatically close stuck dialogs (HumanRelayDialog, DeleteMessageDialog, EditMessageDialog).
  • Implements DialogErrorBoundary in DialogErrorBoundary.tsx to catch and handle errors in dialog content.
  • Adds Escape key handler in App.tsx for manual dialog closure.
  • Logs telemetry events when dialog recovery is triggered.
• Components:
  • Wraps MemoizedHumanRelayDialog, MemoizedDeleteMessageDialog, and MemoizedEditMessageDialog with DialogErrorBoundary in App.tsx.
• Testing:
  • All existing tests pass.
  • Linting and type checking pass.

^{This description was created by for c0d462b. You can customize this summary. It will automatically update as commits are pushed.}

[ellipsis-dev]

Telemetry Logging Order: Consider moving the telemetryClient.capture call before resetting the dialog states so that you log the actual stuck state values. This can help in debugging issues more precisely.

[daniel-lxs]

Issue is not properly scoped