Fix all the old usage of admonition syntax (#107098)

docs/sources/shared/alerts/how_label_matching_works.md

@@ -25,9 +25,9 @@ A label matchers consists of 3 distinct parts, the **label**, the **value** and
   | `=~`     | Select labels that regex-match the value.          |
   | `!~`     | Select labels that do not regex-match the value.   |
 
-{{% admonition type="note" %}}
+{{< admonition type="note" >}}
 If you are using multiple label matchers, they are combined using the AND logical operator. This means that all matchers must match in order to link a rule to a policy.
-{{% /admonition %}}
+{{< /admonition >}}
 
 **Label matching example**
 

docs/sources/shared/alerts/note-dynamic-labels.md

@@ -5,10 +5,10 @@ labels:
 title: 'Note Dynamic labels'
 ---
 
-{{% admonition type="note" %}}
+{{< admonition type="note" >}}
 
 An alert instance is uniquely identified by its set of labels.
 
 - Avoid displaying query values in labels, as this can create numerous alert instances—one for each distinct label set. Instead, use annotations for query values.
 - If a templated label's value changes, it maps to a different alert instance, and the previous instance transitions to the `No data` state when its label value is no longer present.
-  {{% /admonition %}}
+  {{< /admonition >}}

docs/sources/shared/alerts/template-language.md

@@ -165,9 +165,9 @@ This works because both `.Alerts` and `.Alerts.Firing` is a list of alerts.
 {{ end }}
 ```
 
-{{% admonition type="note" %}}
+{{< admonition type="note" >}}
 You cannot create independent, reusable templates for labels and annotations as you can with notification templates. In alert rule templates, you need to write each template inline within the label or annotation field.
-{{% /admonition %}}
+{{< /admonition >}}
 
 ## Comments