feat: limiting the size of query results to Dashboard

[poltao]

I hereby agree to the terms of the GreptimeDB CLA.

Refer to a related PR or issue link (optional)

close #3716

What's changed and what's your intention?

Limit the returned rows to 1000, iff the query comes from Dashboard.

Adding a new source enum to the SqlQuery to identify if it's a request from DashBorad or not, and then handle the flow inside the src/servers/src/http/handler.rs:72. In addition, considering that the dashboard only supports greptimedb_v1 format, only the output of greptimedb_v1 format outputs is processed this PR.

Checklist

• I have written the necessary rustdoc comments.
• I have added the necessary unit tests and integration tests.
• This PR does not require documentation updates.

[codecov]

Codecov Report

Attention: Patch coverage is 95.12195% with 2 lines in your changes are missing coverage. Please review.

Project coverage is 85.50%. Comparing base (be1eb4e) to head (87c80ce).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3901      +/-   ##
==========================================
- Coverage   85.81%   85.50%   -0.31%     
==========================================
  Files         965      965              
  Lines      165015   165056      +41     
==========================================
- Hits       141602   141135     -467     
- Misses      23413    23921     +508     

[evenyag]

We don't need to define the parse() method which is equivalent to from_str().ok().

[tisonkun]

If we go forward in the limit param way, I don't think we should add the RequestSource option that would introduce tech debt.

[poltao]

@MichaelScofield @zyy17 @tisonkun @evenyag PTAL: refactor PR by limit param.

[tisonkun]

LGTM. Thanks for your contribution!