feat(announcements): add markdown support (#1371)

* feat(announcements): add markdown support

* feat(announcements): add information about announcement formatting in readme

* feat(announcements): bump packages versions for marked and dompurify

* feat(announcements): bump versions for marked and dompurify in package-lock.json

* fix(announcements): md to link was not working since the conflict merge

* fix(announcements): fix time before message and not after

* feat(announcements): past announcements add markdown support

* feat(announcements): static files

Author: Sworyz

README.md

@@ -526,7 +526,7 @@ Here are some examples of conditions you can use:
 
 
 ### Announcements
-System-wide announcements allow you to display important messages at the top of the status page. These can be used to inform users about planned maintenance, ongoing issues, or general information.
+System-wide announcements allow you to display important messages at the top of the status page. These can be used to inform users about planned maintenance, ongoing issues, or general information. You can use markdown to format your announcements.
 
 This is essentially what some status page calls "incident communications".
 

web/app/package-lock.json

@@ -15,7 +15,9 @@
     "clsx": "^2.1.1",
     "core-js": "^3.45.0",
     "date-fns": "^4.1.0",
+    "dompurify": "^3.3.0",
     "lucide-vue-next": "^0.539.0",
+    "marked": "^16.4.1",
     "tailwind-merge": "^3.3.1",
     "vue": "^3.5.18",
     "vue-chartjs": "^5.3.2",