Refactor Notices and System Health pane (#24243)

* refactor notices

* show startup message for enrichments in health pane

* tweaks

docs/docs/troubleshooting/faqs.md

@@ -184,6 +184,6 @@ Filters and masks only hide the incorrect result - they don't teach Frigate what
 
 ### Where do I see problems Frigate has detected?
 
-Open System > Health. The Notices list shows problems the backend has noticed on its own, such as a camera whose ffmpeg keeps crashing, a detector that had to be restarted, a model download that failed, or recordings being deleted before their retention period. Entries that describe a one-time event can be dismissed; entries that describe an ongoing condition clear themselves once it is fixed.
+Open System > Health. The Notices list keeps a record of problems Frigate has found, and you can dismiss any entry to acknowledge it. Ongoing conditions, such as an offline camera or recordings deleted before their retention period, appear in the status bar for admins until they clear, and the status bar links to the Notices list while it has undismissed entries. On mobile, tap the warning icon in the bottom navigation bar to see them.
 
 The Hardware section below the notices shows whether the detection hardware, hardware acceleration, and enrichment devices in your config were found and are being used, so a GPU that silently fell back to the CPU shows up as a warning. Run stream checks to probe every camera's streams for the same problems the camera wizard reports.

docs/static/frigate-api.yaml

@@ -4171,13 +4171,13 @@ paths:
       description: |-
         **Access:** Admin role required.
 
-        Get the active notices, most severe first.
+        Get notices, most severe first.
 
         Args:
-            include_dismissed: Also return event notices the user has dismissed
+            include_dismissed: Also return dismissed notices, for the history view
 
         Returns:
-            The active notices
+            The notices
       operationId: get_notices_notices_get
       parameters:
         - name: include_dismissed
@@ -4221,6 +4221,44 @@ paths:
       security:
         - frigateAdminAuth: []
       x-required-role: admin
+  /notices/dismissed_checks:
+    get:
+      tags:
+        - Notices
+      summary: Get Dismissed Checks
+      description: |-
+        **Access:** Admin role required.
+
+        Get the dismissed config and stream check rows, newest first.
+      operationId: get_dismissed_checks_notices_dismissed_checks_get
+      responses:
+        '200':
+          description: Successful Response
+          content:
+            application/json:
+              schema: {}
+      security:
+        - frigateAdminAuth: []
+      x-required-role: admin
+  /notices/dismissed:
+    delete:
+      tags:
+        - Notices
+      summary: Purge Dismissed
+      description: |-
+        **Access:** Admin role required.
+
+        Delete every dismissed notice and check row so each can show again.
+      operationId: purge_dismissed_notices_dismissed_delete
+      responses:
+        '200':
+          description: Successful Response
+          content:
+            application/json:
+              schema: {}
+      security:
+        - frigateAdminAuth: []
+      x-required-role: admin
   /notices/{notice_id}/dismiss:
     post:
       tags:
@@ -4229,7 +4267,9 @@ paths:
       description: |-
         **Access:** Admin role required.
 
-        Hide an event notice until it is raised again.
+        Hide a notice or a config or stream check row.
+
+        It stays hidden if the same problem happens again.
       operationId: dismiss_notice_notices__notice_id__dismiss_post
       parameters:
         - name: notice_id