fix the problem that offset in limit query for tiflash system tables doesn't take effect (#6745)

[ti-chi-bot]

This is an automated cherry-pick of #6745

What problem does this PR solve?

Issue Number: close #6747

Problem Summary: When query tiflash system tables from tidb, tidb will send query like select ... limit offset, 1024. And the query only stops when the num of return rows is less than length. However, the offset parameter is not repected by tiflash, and will always return the same result with any offset value. So if the system table has more than 1024 rows, the query will hang forever.

What is changed and how it works?

Port the implementation from https://github.com/ClickHouse/ClickHouse/blob/19.5/dbms/src/DataStreams/LimitBlockInputStream.cpp#L21

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)

1. deploy a cluster and import data to make the tiflash system tables dt_segments with more than 1024 rows;
2. run the query select count(*) from information_schema.tiflash_segments and make sure it succeeds;

• No code

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Fix the problem that query on tiflash system tables may hang under large amount of data

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has not been approved.

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

The full list of commands accepted by this bot can be found here.

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[ti-chi-bot]

@ti-chi-bot: This cherry pick PR is for a release branch and has not yet been approved by release team.
Adding the do-not-merge/cherry-pick-not-approved label.

To merge this cherry pick, it must first be approved by the collaborators.

AFTER it has been approved by collaborators, please ping the release team in a comment to request a cherry pick review.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.