docs: fix refs to fix links in http api docs (#109429)

docs/sources/developers/http_api/folder.md

@@ -14,13 +14,24 @@ labels:
     - enterprise
     - oss
 title: Folder HTTP API
+refs:
+  apis:
+    - pattern: /docs/grafana/
+      destination: /docs/grafana/<GRAFANA_VERSION>/developers/http_api/apis/
+    - pattern: /docs/grafana-cloud/
+      destination: /docs/grafana-cloud/developer-resources/api-reference/http-api/apis/
+  alerting:
+    - pattern: /docs/grafana/
+      destination: /docs/grafana/<GRAFANA_VERSION>/alerting
+    - pattern: /docs/grafana-cloud/
+      destination: /docs/grafana-cloud/alerting-and-irm/alerting/
 ---
 
 # New Folders APIs
 
 > If you are running Grafana Enterprise, for some endpoints you'll need to have specific permissions. Refer to [Role-based access control permissions](/docs/grafana/latest/administration/roles-and-permissions/access-control/custom-role-actions-scopes/) for more information.
 
-> To view more about the new api structure, refer to [API overview]({{< ref "apis" >}}).
+> To view more about the new api structure, refer to [API overview](ref:apis).
 
 ### Get all folders
 
@@ -28,7 +39,7 @@ title: Folder HTTP API
 
 Returns all folders that the authenticated user has permission to view within the given organization. Use the `limit` query parameter to control the maximum number of dashboards returned. To retrieve additional dashboards, utilize the `continue` token provided in the response to fetch the next page.
 
-- namespace: to read more about the namespace to use, see the [API overview]({{< ref "apis" >}}).
+- namespace: to read more about the namespace to use, see the [API overview](ref:apis).
 
 **Required permissions**
 
@@ -94,7 +105,7 @@ Status Codes:
 
 Will return the folder given the folder uid.
 
-- namespace: to read more about the namespace to use, see the [API overview]({{< ref "apis" >}}).
+- namespace: to read more about the namespace to use, see the [API overview](ref:apis).
 - uid: the unique identifier of the folder to update. this will be the _name_ in the folder response
 
 **Required permissions**
@@ -156,7 +167,7 @@ Status Codes:
 
 Creates a new folder.
 
-- namespace: to read more about the namespace to use, see the [API overview]({{< ref "apis" >}}).
+- namespace: to read more about the namespace to use, see the [API overview](ref:apis).
 
 **Required permissions**
 
@@ -238,7 +249,7 @@ Status Codes:
 
 Updates an existing folder identified by uid.
 
-- namespace: to read more about the namespace to use, see the [API overview]({{< ref "apis" >}}).
+- namespace: to read more about the namespace to use, see the [API overview](ref:apis).
 - uid: the unique identifier of the folder to update. this will be the _name_ in the folder response
 
 **Required permissions**
@@ -328,9 +339,9 @@ Content-Length: 97
 
 Deletes an existing folder identified by UID along with all dashboards (and their alerts) stored in the folder. This operation cannot be reverted.
 
-If [Grafana Alerting]({{< relref "/docs/grafana/latest/alerting" >}}) is enabled, you can set an optional query parameter `forceDeleteRules=false` so that requests will fail with 400 (Bad Request) error if the folder contains any Grafana alerts. However, if this parameter is set to `true` then it will delete any Grafana alerts under this folder.
+If [Grafana Alerting](ref:alerting) is enabled, you can set an optional query parameter `forceDeleteRules=false` so that requests will fail with 400 (Bad Request) error if the folder contains any Grafana alerts. However, if this parameter is set to `true` then it will delete any Grafana alerts under this folder.
 
-- namespace: to read more about the namespace to use, see the [API overview]({{< ref "apis" >}}).
+- namespace: to read more about the namespace to use, see the [API overview](ref:apis).
 - uid: the unique identifier of the folder to delete. this will be the _name_ in the folder response
 
 **Required permissions**