Add Investigate action to Critical Issues that navigates to relevant view

[erikdarlingdata]

Summary

Critical Issues today is a dead-end grid. It tells you "high CPU detected" or "blocking storm" but there's no way to jump to the relevant view. The user has to read the message, mentally map it to a tab, switch tabs, and set the right time range.

Proposed Behavior

An "Investigate" button (or double-click) on each issue row that:

1. Navigates to the relevant tab (blocking, queries, memory, etc.)
2. Pre-sets the time range to the incident window
3. Optionally pre-filters to the affected database

Issue-to-View Mapping

Issue Category	Target View	Pre-set
High CPU	Query Performance → Top Queries	Time range around spike
Blocking Storm	Blocking → Blocked Process Reports	Time range, slicer if available
Deadlocks	Blocking → Deadlocks	Time range around events
Memory Pressure	Memory → Overview	Time range around pressure event
I/O Latency	File I/O → Latency	Time range
TempDB Pressure	TempDB	Time range

Design Notes

• This turns Critical Issues from a notification log into a launch pad
• The difference between "you have a problem" and "here's the problem"
• Each issue already has a timestamp and problem area — those map directly to target tab + time range
• Applies to both Dashboard and Lite
• Dashboard uses event-based navigation (similar to ViewPlanRequested pattern); Lite uses direct tab selection

[erikdarlingdata]

Implementation order: Lite first, then port to Dashboard once the pattern is validated. This avoids the complexity of iterating on both apps simultaneously.

[erikdarlingdata]

Implemented in PR #702. Investigate button navigates to relevant tab with incident time window, populates global date pickers for Apply to All. Config issues show investigate query dialog.