util: optimize the performance of restore with db (#22910)

[ti-srebot]

cherry-pick #22910 to release-4.0
You can switch your code base to this Pull Request by using git-extras:

# In tidb repo:
git pr https://github.com/pingcap/tidb/pull/23283

After apply modifications, you can push your change to this PR via:

git push git@github.com:ti-srebot/tidb.git pr/23283:release-4.0-276dd0e69e3d

---

What problem does this PR solve?

Issue Number: close #22398

Problem Summary:

We use restore to generate SQL with default DB, it will consume more CPU. This problem will be more prominent in batch insert, because insert is usually faster. Also, the column list and the value list can be very long.

In order to deal with this situation, for a simple insert, we do not use restore but string replacement.

Related changes

• Need to cherry-pick to the release branch

Check List

Tests

• Unit test

Side effects

• Performance regression
  • Consumes more CPU
• Breaking backward compatibility

Release note

• optimize the performance of restore with DB

[ti-srebot]

/run-all-tests

[ti-srebot]

@rebelice you're already a collaborator in bot's repo.

[djshow832]

It's a release-blocker, could you update this PR? @rebelice

[Reminiscent]

/LGTM

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• Reminiscent
• qw4990

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.

[rebelice]

It's a release-blocker, could you update this PR? @rebelice

I can not merge this PR now, because v4.0.12 is frozen.