set cop request schema version in client-c

[lidezhu]

What problem does this PR solve?

Issue Number: close #3967

Problem Summary: When do remote read, tiflash doesn't set schema version on the dag request. And if the schema info in the target machine is outdated, it will not try to sync schema, so it may raise some error like "Invalidate column id".
In previous fix: #4021, we just set schema version in tiflash code base. But the schema version is not passed to client-c.

What is changed and how it works?

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• 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

None

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• windtalker

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.

[windtalker]

LGTM

[lidezhu]

/merge

[ti-chi-bot]

@lidezhu: It seems you want to merge this PR, I will help you trigger all the tests:

/run-all-tests

You only need to trigger /merge once, and if the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

If you have any questions about the PR merge process, please refer to pr process.

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 ti-community-infra/tichi repository.

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: 576d5e7

[sre-bot]

Coverage for changed files

no c/c++ source change detected

Coverage summary

Functions  MissedFunctions  Executed  Lines   MissedLines  Cover
16674      9491             43.08%    184376  95863        48.01%

full coverage report (for internal network access only)

[ti-chi-bot]

In response to a cherrypick label: failed to apply #4090 on top of branch "release-4.0":

[failed to git add conflicting files: exit status 128, failed to git commit: exit status 128]

[ti-chi-bot]

In response to a cherrypick label: failed to apply #4090 on top of branch "release-5.0":

[failed to git add conflicting files: exit status 128, failed to git commit: exit status 128]

[ti-chi-bot]

In response to a cherrypick label: failed to apply #4090 on top of branch "release-5.1":

[failed to git add conflicting files: exit status 128, failed to git commit: exit status 128]

[ti-chi-bot]

In response to a cherrypick label: failed to apply #4090 on top of branch "release-5.2":

[failed to git add conflicting files: exit status 128, failed to git commit: exit status 128]

[ti-chi-bot]

In response to a cherrypick label: failed to apply #4090 on top of branch "release-5.3":

[failed to git add conflicting files: exit status 128, failed to git commit: exit status 128]

[ti-chi-bot]

In response to a cherrypick label: failed to apply #4090 on top of branch "release-5.4":

[failed to git add conflicting files: exit status 128, failed to git commit: exit status 128]

[lidezhu]

This pr will be manually cherry picked to the cherry pick pr of this pr:#4021