TOC Sync: Move alerting and recording rules under Alert. (#8805)

**Which issue(s) this PR fixes**:
Fixes #8717 

**Special notes for your reviewer**:
Part of the Database products table of contents alignment project.
Moves alerting and recording rules from Rules to new Alert heading in
TOC.
Updates front matter for the topic.
Fixes links broken by the move.

docs/sources/alert/_index.md

@@ -1,12 +1,22 @@
 ---
+title: Alerting and recording rules
+menuTitle: Alert
+description: Learn how the rule evaluates queries for alerting.
+
 aliases:
-  - /alerting/
-title: Alerting and Recording Rules
-description: Alerting and Recording Rules
-weight: 700
+  - /docs/loki/latest/rules/
+  - docs/loki/latest/alert/
+  - docs/loki/latest/alerting/
+
+weight: 850
+keywords:
+  - loki
+  - alert
+  - alerting
+  - ruler
 ---
 
-# Alerting and Recording Rules
+# Alerting and recording rules
 
 Grafana Loki includes a component called the ruler. The ruler is responsible for continually evaluating a set of configurable queries and performing an action based on the result.
 

docs/sources/operations/blocking-queries.md

@@ -45,4 +45,4 @@ Blocked queries are logged, as well as counted in the `loki_blocked_queries` met
 
 ## Scope
 
-Queries received via the API and executed as [alerting/recording rules]({{<relref "../rules">}}) will be blocked.
+Queries received via the API and executed as [alerting/recording rules]({{<relref "../alert">}}) will be blocked.

docs/sources/release-notes/v2-3.md

@@ -19,7 +19,7 @@ Some parts of the Loki repo will remain Apache-2.0 licensed (mainly clients and
 * Loki now has the ability to apply [custom retention]({{<relref "../operations/storage/retention">}}) based on stream selectors! This will allow much finer control over log retention all of which is now handled by Loki, no longer requiring the use of object store configs for retention.
 * Coming along hand in hand with storing logs for longer durations is the ability to [delete log streams]({{<relref "../operations/storage/logs-deletion">}}). The initial implementation lets you submit delete request jobs which will be processed after 24 hours.
 * A very exciting new LogQL parser has been introduced: the [pattern parser]({{<relref "../logql/log_queries#parser-expression">}}). Much simpler and faster than regexp for log lines that have a little bit of structure to them such as the [Common Log Format](https://en.wikipedia.org/wiki/Common_Log_Format). This is now Loki's fastest parser so try it out on any of your log lines!
-* Extending on the work of Alerting Rules, Loki now accepts [recording rules]({{<relref "../rules/#recording-rules">}}). This lets you turn your logs into metrics and push them to Prometheus or any Prometheus compatible remote_write endpoint.
+* Extending on the work of Alerting Rules, Loki now accepts [recording rules]({{<relref "../alert/#recording-rules">}}). This lets you turn your logs into metrics and push them to Prometheus or any Prometheus compatible remote_write endpoint.
 * LogQL can understand [IP addresses]({{<relref "../logql/ip">}})! This enables filtering on IP addresses and subnet ranges.
 
 For those of you running Loki as microservices, the following features will improve performance operations significantly for many operations.

docs/sources/release-notes/v2-4.md

@@ -16,7 +16,7 @@ Loki 2.4 focuses on two items:
 * [**Loki no longer requires logs to be sent in perfect chronological order.**]({{<relref "../configuration/#accept-out-of-order-writes">}}) Support for out of order logs is one of the most highly requested features for Loki. The strict ordering constraint has been removed.
 * Scaling Loki is now easier with a hybrid deployment mode that falls between our single binary and our microservices. The [Simple scalable deployment]({{<relref "../fundamentals/architecture/deployment-modes">}}) scales Loki with new `read` and `write` targets. Where previously you would have needed Kubernetes and the microservices approach to start tapping into Loki’s potential, it’s now possible to do this in a simpler way.
 * The new [`common` section]({{<relref "../configuration/#common">}}) results in a 70% smaller Loki configuration. Pair that with updated defaults and Loki comes out of the box with more appropriate defaults and limits. Check out the [example local configuration](https://github.com/grafana/loki/blob/main/cmd/loki/loki-local-config.yaml) as the new reference for running Loki.
-* [**Recording rules**]({{<relref "../rules/#recording-rules">}}) are no longer an experimental feature. We've given them a more resilient implementation which leverages the existing write ahead log code in Prometheus.
+* [**Recording rules**]({{<relref "../alert/#recording-rules">}}) are no longer an experimental feature. We've given them a more resilient implementation which leverages the existing write ahead log code in Prometheus.
 * The new [**Promtail Kafka Consumer**]({{<relref "../clients/promtail/scraping/#kafka">}}) can easily get your logs out of Kafka and into Loki.
 * There are **nice LogQL enhancements**, thanks to the amazing Loki community. LogQL now has [group_left and group_right]({{<relref "../logql/#many-to-one-and-one-to-many-vector-matches">}}). And, the `label_format` and `line_format` functions now support [working with dates and times]({{<relref "../logql/template_functions/#now">}}).
 * Another great community contribution allows Promtail to [**accept ndjson and plaintext log files over HTTP**]({{<relref "../clients/promtail/configuration/#loki_push_api">}}).