br/restore: add version check for backup schema_version (#929)

[ti-chi-bot]

This is an automated cherry-pick of #929

What problem does this PR solve?

a special fix for v4.0 versions of #790

Because #685 cannot be cherry-picked to release-4.0, 4.0.x BR would corrupt 4.0 clusters without even a warn message when the backup archive come from a table with non-int clustered primary key. This PR would add a check to the backup archive version, and intercept restoring from incompatible backup archives.

What is changed and how it works?

CheckClusterVersion was changed to check version in different way.
And added a check to cluster version stored in backupmeta during restore. (after reading backup meta)

Currently, this check only checks major versions (because of clustered index).

Check List

Tests

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

Code changes

• Has exported function/method change
  signature change for CheckClusterVersion.

- CheckClusterVersion(ctx context.Context, client pd.Client) error
+ CheckClusterVersion(ctx context.Context, client pd.Client, checker VerChecker) error

Release Note

• BR would check cluster version of backup now.

[lonng]

/lgtm

[3pointer]

/lgtm

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• 3pointer
• lonng

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 writing /lgtm in a comment.
Reviewer can cancel approval by writing /lgtm cancel in a comment.

[lonng]

/merge

[ti-chi-bot]

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

Commit hash: 0981f40

[ti-chi-bot]

@ti-chi-bot: Your PR was out of date, I have automatically updated it for you.

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.