ensure every record in wal is only applied once when restart (#7920)

[ti-chi-bot]

This is an automated cherry-pick of #7920

What problem does this PR solve?

Issue Number:

Problem Summary:
After dumping snapshot to checkpoint file, we only remove log files which max sequence is smaller than the sequence used to dump snapshot.
So the remaining wal files may have some overlap with the checkpoint file.
And at restart, we will apply all records in the checkpoint file and other wal files which will cause some records to be applied more than once.
This may cause some problem like the following picture.

Because page 88 was already deleted, it is not shown in the checkpoint file log_100_1. But the operation ref 90 -> 88 is still in later log files. So at restart, when it try to apply this record, it will fail to complete the ref operation.

What is changed and how it works?

Record the snap sequence used to dump checkpoint in the filename of checkpoint file. Specifically, change it from log_100_1 to log_100_1_400.
When restart, after apply all records in checkpoint file, we will skip later record which sequence is smaller than the snap sequence in the checkpoint file name.

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
  • Can not downgrade to a version earlier than v7.4.0

Documentation

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

Release note

Fix the problem that tiflash may fail to restart under some cases.

[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.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign ilovesoup for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[lidezhu]

/run-all-tests