Device Health: Make the warnings less aggressive

[larsll]

• Latency 95% was triggering too quickly, esp. if the mean latency was very low.
• Delay triggering of warning to 3 reporting periods after starting inference.

[Copilot]

Pull Request Overview

This pull request updates the warning thresholds to make them less aggressive by increasing the delay before triggering warnings and refactoring status comparison logic.

• Delay warnings to trigger after 3 reporting periods instead of 2.
• Introduce a new helper function, statusMinMax, for comparing device statuses.

Comments suppressed due to low confidence (2)

website/src/components/device-status-panel.tsx:174

• [nitpick] The function name 'statusMinMax' could be made more descriptive (e.g., 'selectStatusByPriority') to clarify its purpose of choosing a status based on comparison of priorities.

const statusMinMax = (

website/src/components/device-status-panel.tsx:179

• The statusPriority mapping in statusMinMax differs from the existing getStatusPriority function (which uses lower values for error and warning). Please verify that the updated priority values (error: 4, warning: 3, etc.) are intentional and consistent with the overall device status logic.

const statusPriority = {