[feat] docs; update admonition syntax (#68842)

* [feat] docs; update admonition syntax

- Standardizes according to style conventions: https://grafana.com/docs/writers-toolkit/style-guide/style-conventions/#admonitions
- Prepares docs for better, uniform admonition style.

* Remove false positives and irregularities

* false positive removal

* Update docs/sources/datasources/mysql/_index.md

* Update docs/sources/developers/angular_deprecation/angular-plugins.md

* fix link errors

* Prettify some nested blockquotes

* remoe unnecessary admonition

docs/sources/datasources/prometheus/_index.md

@@ -135,7 +135,9 @@ For details on AWS SigV4, refer to the [AWS documentation](https://docs.aws.amaz
 
 #### AWS Signature Version 4 authentication
 
-> **Note:** Available in Grafana v7.3.5 and higher.
+{{% admonition type="note" %}}
+Available in Grafana v7.3.5 and higher.
+{{% /admonition %}}
 
 To connect the Prometheus data source to Amazon Managed Service for Prometheus using SigV4 authentication, refer to the AWS guide to [Set up Grafana open source or Grafana Enterprise for use with AMP](https://docs.aws.amazon.com/prometheus/latest/userguide/AMP-onboard-query-standalone-grafana.html).
 
@@ -143,7 +145,9 @@ If you run Grafana in an Amazon EKS cluster, follow the AWS guide to [Query usin
 
 ### Configure exemplars
 
-> **Note:** Available in Prometheus v2.26 and higher with Grafana v7.4 and higher.
+{{% admonition type="note" %}}
+Available in Prometheus v2.26 and higher with Grafana v7.4 and higher.
+{{% /admonition %}}
 
 Grafana 7.4 and higher can show exemplars data alongside a metric both in Explore and in Dashboards.
 Exemplars associate higher-cardinality metadata from a specific event with traditional time series data.

docs/sources/datasources/prometheus/query-editor/index.md

@@ -85,8 +85,10 @@ The **Type** setting selects the query type.
 
 - An **Exemplars** query runs with the regular query and shows exemplars in the graph.
 
-> **Note:** Grafana modifies the request dates for queries to align them with the dynamically calculated step.
-> This ensures a consistent display of metrics data, but it can result in a small gap of data at the right edge of a graph.
+{{% admonition type="note" %}}
+Grafana modifies the request dates for queries to align them with the dynamically calculated step.
+This ensures a consistent display of metrics data, but it can result in a small gap of data at the right edge of a graph.
+{{% /admonition %}}
 
 ## Code mode
 
@@ -118,7 +120,9 @@ When you select a metric, the browser narrows down the available labels to show
 You can then select one or more labels for which the available label values are shown in lists in the bottom section.
 Select one or more values for each label to tighten your query scope.
 
-> **Note:** If you do not remember a metric name to start with, you can also select a few labels to narrow down the list, then find relevant label values.
+{{% admonition type="note" %}}
+If you do not remember a metric name to start with, you can also select a few labels to narrow down the list, then find relevant label values.
+{{% /admonition %}}
 
 All lists in the metrics browser have a search field above them to quickly filter for metrics or labels that match a certain string.
 The values section has only one search field, and its filtering applies to all labels to help you find values across labels once selected.

docs/sources/datasources/prometheus/template-variables/index.md

@@ -63,7 +63,9 @@ Regex:
 
 ## Use `$__rate_interval`
 
-> **Note:** Available in Grafana v7.2 and higher.
+{{% admonition type="note" %}}
+Available in Grafana v7.2 and higher.
+{{% /admonition %}}
 
 We recommend using `$__rate_interval` in the `rate` and `increase` functions instead of `$__interval` or a fixed interval value.
 Because `$__rate_interval` is always at least four times the value of the Scrape interval, it avoid problems specific to Prometheus.