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

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/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
 

docs/sources/shared/alerts/warning-provisioning-tree.md

@@ -2,7 +2,7 @@
 title: 'Warning Provisioning Tree'
 ---
 
-{{% admonition type="warning" %}}
+{{< admonition type="warning" >}}
 
 Since the policy tree is a single resource, provisioning it will overwrite all policies in the notification policy tree. However, it does not affect internal policies created when alert rules directly select a contact point.