br/restore: use a new algorithm for batching, deprecating --ddl-batch-size

[YuJuncen]

What problem does this PR solve?

Issue Number: close #55639

Problem Summary:
See the issue.

What changed and how does it work?

Now, we will fetch the max raft entry size from TiKV. And try to batching to the size to 7/8 of the max raft entry size.

Check List

Tests

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

I have tested restoring about 500k tables. The total number of DDLs decreased about 1/2. But the speed of creating table not increased. (About 32 mins for creating all tables for both master and this patch.).

• No need to test

  • I checked and no code files have been changed.

Release note

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

By using a new algorithm for batching `CREATE TABLE` DDLs, we have reduced the number of jobs needed for creating tables. Also the old configuration `--ddl-batch-size` was deprecated.

[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 ask for approval from yujuncen, 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

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

[tiprow]

Hi @YuJuncen. 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.

[ti-chi-bot]

PR needs rebase.

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.