redesign to emphasize longitudinal stats

[pstaylor-patrick]

Related to #7

👋 TL;DR

This PR replaces the existing platform status cards on the dashboard with a new latency analytics dashboard. It introduces new components for visualizing connection status and latency metrics (compact-connection-status, latency-chart, latency-stats-row), refactors the analytics logic into modular components, and adds supporting utilities and constants.

🔎 Details

The changes focus on enhancing the application's latency monitoring capabilities by introducing a dedicated analytics dashboard. The core change is the replacement of platform status cards with the new LatencyAnalytics component. This involved:

• Refactoring the existing latency analytics logic into modular components.
• Creating new React components: CompactConnectionStatus, LatencyChart (for visualizing platform performance), and LatencyStatsRow (for platform comparison).
• Adding supporting files: latency constants, chart utilities, and a latency color utility for query results.
• Exporting the LatencyAnalyticsState type from the use-latency-analytics hook for better type sharing.
• Adding the pnpm-lock.yaml file to lock project dependencies.

✅ How to Test

1. Build Verification: Ensure the application builds successfully with the new dependencies.
2. Dashboard Rendering: Navigate to the main dashboard and confirm the platform status cards have been replaced by the new latency analytics dashboard.
3. New Components: Verify the new components (CompactConnectionStatus, LatencyChart, LatencyStatsRow) render correctly within the dashboard.
4. Analytics Functionality: Interact with the latency analytics dashboard to ensure data visualization (charts, stats rows) works as expected and reflects platform performance.
5. Integration: Test that the analytics state is correctly passed to and used by the LatencyAnalytics component.
6. Regression: Verify core application workflows unrelated to the dashboard remain functional.

🥜 GIF