incorrect and unstable output when using limit request parameter

[eduardbareev]

Describe the bug

this is about limit request parameter, not the pipe one

curl --no-progress-meter 'http://rck9thr.test:9428/select/logsql/query' \
    --data-urlencode query='_time:[0, now] | sort by (_time desc)  ' \
    --data-urlencode limit=1000 \
    | wc -l
45

curl --no-progress-meter 'http://rck9thr.test:9428/select/logsql/query' \
    --data-urlencode query='_time:[0, now] | sort by (_time desc)  ' \
    --data-urlencode limit=1000 \
    | wc -l
44

curl --no-progress-meter 'http://rck9thr.test:9428/select/logsql/query' \
    --data-urlencode query='_time:[0, now] | sort by (_time desc)  ' \
    --data-urlencode limit=1000 \
    | wc -l
45

curl --no-progress-meter 'http://rck9thr.test:9428/select/logsql/query' \
    --data-urlencode query='_time:[0, now] | sort by (_time desc)  ' \
    --data-urlencode limit=1000 \
    | wc -l
55


curl --no-progress-meter 'http://rck9thr.test:9428/select/logsql/query' \
    --data-urlencode query='_time:[0, now] | sort by (_time desc)  ' \
    --data-urlencode limit=1000 \
    | wc -l
45

To Reproduce

maybe datadir can help vicloglimitrequstparam.tag.gz

Version

victoria-logs-20240515-025846-tags-v0.7.0-victorialogs-0-g6fdba8599d