docs/victorialogs/querying/README.md: group the description for the time-based query args at /select/logsql/stats_query and /select/logsql/stats_query_range docs

Previously the description for `time`, `start`, `end` and `step` query args was split into two parts
with the description for the `query` query arg in the middle. This complicated reading the docs.

Author: valyala

docs/victorialogs/querying/README.md

@@ -452,6 +452,9 @@ VictoriaLogs provides `/select/logsql/stats_query?query=<query>&time=<t>` HTTP e
 for the given [`query`](https://docs.victoriametrics.com/victorialogs/logsql/) at the given timestamp `t`
 in the format compatible with [Prometheus querying API](https://prometheus.io/docs/prometheus/latest/querying/api/#instant-queries).
 
+The `<t>` arg can contain values in [any supported format](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/#timestamp-formats).
+If `<t>` is missing, then it equals to the current time.
+
 The `<query>` must contain [`stats` pipe](https://docs.victoriametrics.com/victorialogs/logsql/#stats-pipe). The calculated stats is converted into metrics
 with labels from `by(...)` clause of the `| stats by(...)` pipe.
 
@@ -461,9 +464,6 @@ and [`row_max`](https://docs.victoriametrics.com/victorialogs/logsql/#row_max-st
 Additional labels can be created from metrics via [`format` pipe](https://docs.victoriametrics.com/victorialogs/logsql/#format-pipe).
 Additional metrics can be created from the existing metrics via [`math` pipe](https://docs.victoriametrics.com/victorialogs/logsql/#math-pipe).
 
-The `<t>` arg can contain values in [any supported format](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/#timestamp-formats).
-If `<t>` is missing, then it equals to the current time.
-
 For example, the following command returns the number of logs per each `level` [field](https://docs.victoriametrics.com/victorialogs/keyconcepts/#data-model)
 across logs over `2024-01-01` day by UTC:
 
@@ -515,6 +515,7 @@ Below is an example JSON output returned from this endpoint:
 ```
 
 The `/select/logsql/stats_query` API is useful for generating Prometheus-compatible alerts and calculating recording rules results.
+It is used by [vmalert](https://docs.victoriametrics.com/victorialogs/vmalert/).
 
 The `/select/logsql/stats_query` returns the following additional HTTP response headers:
 
@@ -535,6 +536,17 @@ VictoriaLogs provides `/select/logsql/stats_query_range?query=<query>&start=<sta
 for the given [`query`](https://docs.victoriametrics.com/victorialogs/logsql/) on the given `[start ... end)` time range with the given `step` interval.
 The stats is returned in the format compatible with [Prometheus querying API](https://prometheus.io/docs/prometheus/latest/querying/api/#range-queries).
 
+The `<start>` and `<end>` args can contain values in [any supported format](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/#timestamp-formats).
+If `<start>` is missing, then it equals to the minimum timestamp across logs stored in VictoriaLogs.
+If `<end>` is missing, then it equals to the maximum timestamp across logs stored in VictoriaLogs.
+
+The `<step>` arg can contain values in [the format specified here](https://docs.victoriametrics.com/victorialogs/logsql/#stats-by-time-buckets).
+If `<step>` is missing, then it equals to `1d` (one day).
+
+Note: The `/select/logsql/stats_query_range` endpoint
+relies on `_time` field for time bucketing and therefore does not allow any pipe to change or remove the `_time` before the `| stats ...` pipe.
+In contrast, queries passed to [`/select/logsql/stats_query`](https://docs.victoriametrics.com/victorialogs/querying/#querying-log-stats) can include any pipes before the `| stats ...` pipe, including pipes that modify or remove the `_time` field.
+
 The `<query>` must contain [`stats` pipe](https://docs.victoriametrics.com/victorialogs/logsql/#stats-pipe). The calculated stats is converted into metrics
 with labels from `by(...)` clause of the `| stats by(...)` pipe.
 
@@ -548,17 +560,6 @@ It may be useful to use [`running_stats`](https://docs.victoriametrics.com/victo
 and [`total_stats`](https://docs.victoriametrics.com/victorialogs/logsql/#total_stats-pipe) pipes for calculating running and total stats over the stats
 returned by the [`stats` pipe](https://docs.victoriametrics.com/victorialogs/logsql/#stats-pipe).
 
-The `<start>` and `<end>` args can contain values in [any supported format](https://docs.victoriametrics.com/victoriametrics/single-server-victoriametrics/#timestamp-formats).
-If `<start>` is missing, then it equals to the minimum timestamp across logs stored in VictoriaLogs.
-If `<end>` is missing, then it equals to the maximum timestamp across logs stored in VictoriaLogs.
-
-The `<step>` arg can contain values in [the format specified here](https://docs.victoriametrics.com/victorialogs/logsql/#stats-by-time-buckets).
-If `<step>` is missing, then it equals to `1d` (one day).
-
-Note: The `/select/logsql/stats_query_range` endpoint
-relies on `_time` field for time bucketing and therefore does not allow any pipe to change or remove the `_time` before the `| stats ...` pipe.
-In contrast, queries passed to [`/select/logsql/stats_query`](https://docs.victoriametrics.com/victorialogs/querying/#querying-log-stats) can include any pipes before the `| stats ...` pipe, including pipes that modify or remove the `_time` field.
-
 For example, the following command returns the number of logs per each `level` [field](https://docs.victoriametrics.com/victorialogs/keyconcepts/#data-model)
 across logs over `2024-01-01` day by UTC with 6-hour granularity:
 
@@ -628,6 +629,7 @@ Below is an example JSON output returned from this endpoint:
 ```
 
 The `/select/logsql/stats_query_range` API is useful for generating Prometheus-compatible graphs in Grafana.
+It is used by [Grafana plugin for VictoriaLogs](https://docs.victoriametrics.com/victorialogs/integrations/grafana/).
 
 The `/select/logsql/stats_query_range` returns the following additional HTTP response headers: