br: PiTR table filter online support

[Tristan1900]

What problem does this PR solve?

Issue Number: close #59280

Problem Summary:

What changed and how does it work?

Make sure when user wants to use PiTR table filter to restore to an online cluster, the flag --online is specified.

1. Figure out all the tables needed for the entire PiTR at snapshot restore phase, and check current cluster to see any table exist so error out early.
2. For tables created during snapshot backup, set tableMode to restore to block any user op
3. Make sure to populate table name to final state for renamed tables to avoid any table name conflicts.
4. During log replay at log restore phase, set all tableInfo to restoreMode and set table name to final name as well
5. After restore finishes, set tableMode back to normal mode, so it can unblock user op and fetches the latest value from TiKV written by the log restore.

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]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[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 ailinkid, wjhuang2016, yujuncen for approval, 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:

• OWNERS
• br/OWNERS
• pkg/ddl/OWNERS
• pkg/infoschema/OWNERS
• pkg/meta/OWNERS
• pkg/planner/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 @Tristan1900. 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 74.29112% with 136 lines in your changes missing coverage. Please review.

Project coverage is 74.4271%. Comparing base (0a109e9) to head (dbd5985).
Report is 1 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #59281        +/-   ##
================================================
+ Coverage   73.1153%   74.4271%   +1.3118%     
================================================
  Files          1702       1748        +46     
  Lines        470060     478426      +8366     
================================================
+ Hits         343686     356079     +12393     
+ Misses       105188      99744      -5444     
- Partials      21186      22603      +1417     

Flag	Coverage Δ
integration	46.8548% <74.2424%> (?)

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

Components	Coverage Δ
dumpling	52.6910% <ø> (ø)
parser	∅ <ø> (∅)
br	61.7164% <74.2911%> (+14.5131%)	⬆️

🚀 New features to boost your workflow:

• ❄ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[ti-chi-bot]

@Tristan1900: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
idc-jenkins-ci-tidb/check_dev	dbd5985	link	true	/test check-dev
idc-jenkins-ci-tidb/build	dbd5985	link	true	/test build
pull-unit-test-ddlv1	dbd5985	link	true	/test pull-unit-test-ddlv1
idc-jenkins-ci-tidb/unit-test	dbd5985	link	true	/test unit-test
idc-jenkins-ci-tidb/check_dev_2	dbd5985	link	true	/test check-dev2
pull-br-integration-test	dbd5985	link	true	/test pull-br-integration-test

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.