docs: Add compareDateRange example (#8307) — thanks @EduardoGHdez!

* Fix links to #regular-query section

* docs/apis: Add compareDateRange example

* docs/apis: Update "Regular Query" REST example

Some of the cube-js-sdks take care of using the right params, but
when the api is reached through a plain http client, it's expected to
have the `query` param in the request body, which wasn't exemplified
here

* docs/api-integration: Unwrap rest-examples out of query

* Tiny fixes

---------

Co-authored-by: Igor Lukanin <[email protected]>

Author: EduardoGHdez

docs/pages/product/apis-integrations/queries.mdx

@@ -272,21 +272,51 @@ GROUP BY 1, 2;
 ### Compare date range query
 
 **Compare date range queries are special cases of regular queries.**
-Similarly to [regular queries](#regular-queries), they include lists of
+Similarly to [regular queries](#regular-query), they include lists of
 dimensions and measures, filters, etc. and return a result set.
 
 However, unlike regular queries, they provide a convenient way to retrieve
-measure values for *more than one date range* for a time dimension. See [this
-blog post][blog-compare-date-range] for more details and examples.
+measure values for *more than one date range* for a time dimension.
 
 You can make a compare date range query by using the `compareDateRange`
-option with the [REST API][ref-rest-api-query-format-options-tdf]. For the SQL
-API, you can write an equivalent query using the `UNION ALL` statement.
+option with the [REST API][ref-rest-api-query-format-options-tdf]. Note that
+you also need to set the `queryType` parameter of the [`/v1/load`
+endpoint][ref-rest-api-load] to `regular`.
+
+#### Example
+
+```json
+{
+  "dimensions": ["orders.city"],
+  "measures": ["orders.amount"],
+  "filters": [
+    {
+      "member": "orders.status",
+      "operator": "equals",
+      "values": ["shipped"]
+    }
+  ],
+  "timeDimensions": [{
+    "dimension": "orders.created_at",
+    "compareDateRange": [
+      ["2024-01-01", "2024-12-31"],
+      ["2023-01-01", "2023-12-31"],
+      ["2022-01-01", "2022-12-31"],
+    ],
+    "granularity": "year",
+  }],
+  "limit": 100
+}
+```
+
+See [this blog post][blog-compare-date-range] for more details and examples.
+
+For the SQL API, you can write an equivalent query using the `UNION ALL` statement.
 
 ### Total query
 
 **Total queries are special cases of regular queries.**
-Similarly to [regular queries](#regular-queries), they include lists of
+Similarly to [regular queries](#regular-query), they include lists of
 dimensions and measures, filters, etc. and return a result set.
 
 In addition to that, they provide a convenient way to retrieve the total number
@@ -300,7 +330,7 @@ equivalent query using the `UNION ALL` statement.
 
 ### Ungrouped query
 
-Similarly to [regular queries](#regular-queries), ungrouped queries include
+Similarly to [regular queries](#regular-query), ungrouped queries include
 lists of dimensions and measures, filters, etc. and return a result set.
 
 However, unlike for regular queries, Cube will not add the
@@ -329,6 +359,7 @@ Additionally, note that ungrouped queries have additional requirements for
 [ref-apis]: /product/apis-integrations
 [ref-sql-api]: /product/apis-integrations/sql-api
 [ref-rest-api]: /product/apis-integrations/rest-api
+[ref-rest-api-load]: /reference/rest-api#v1load
 [ref-graphql-api]: /product/apis-integrations/graphql-api
 [ref-data-sources]: /product/configuration/data-sources
 [ref-rest-api-query-format-options]: /product/apis-integrations/rest-api/query-format#query-properties
@@ -343,4 +374,4 @@ Additionally, note that ungrouped queries have additional requirements for
 [ref-caching]: /product/caching
 [ref-query-rewrite]: /reference/configuration/config#query_rewrite
 [ref-ref-sql-api]: /reference/sql-api
-[blog-compare-date-range]: https://cube.dev/blog/comparing-data-over-different-time-periods
+[blog-compare-date-range]: https://cube.dev/blog/comparing-data-over-different-time-periods