br: add log restore ts into snapshot checkpoint metadata

[Leavrth]

What problem does this PR solve?

Issue Number: ref #57613

Problem Summary:
The filter feature is determined by the PITR restored ts. If the user specify another restored ts in the second execution, the final filtered tables may be different.

What changed and how does it work?

Add log restored ts into the snapshot restore checkpoint metadata so that BR can promise the same log restored ts before log restore checkpoint metadata is saved.

Check List

Tests

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

  • I checked and no code files have been changed.

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

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[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 ask for approval from leavrth, ensuring that each of them provides their approval before proceeding. For more information see the 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:

• br/OWNERS

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

[tiprow]

Hi @Leavrth. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

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-sigs/prow repository.

[codecov]

Codecov Report

Attention: Patch coverage is 50.00000% with 8 lines in your changes missing coverage. Please review.

Project coverage is 74.6262%. Comparing base (42075e6) to head (8fa1d0b).
Report is 4 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #59678        +/-   ##
================================================
+ Coverage   72.9626%   74.6262%   +1.6635%     
================================================
  Files          1694       1714        +20     
  Lines        468752     469946      +1194     
================================================
+ Hits         342014     350703      +8689     
+ Misses       105682      97413      -8269     
- Partials      21056      21830       +774     

Flag	Coverage Δ
integration	46.1293% <50.0000%> (?)
unit	72.2113% <0.0000%> (+0.0444%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	52.6910% <ø> (ø)
parser	∅ <ø> (∅)
br	61.3273% <50.0000%> (+16.2751%)	⬆️