ddl: wrap the sessionctx to public delete range logic to BR (#48050)

[ti-chi-bot]

This is an automated cherry-pick of #48050

What problem does this PR solve?

Issue Number: close #47738

Problem Summary:
Currently we implement the same delete range logic as ddl's. But it's too expensive to keep in sync with ddl's delete range logic. Therefore, there is a plan to move it back.

What is changed and how it works?

wrap the sessionctx to public delete range logic to BR

Check List

Tests

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

1. I run the SQL br/tests/br_pitr/prepare_data/delete_range.sql and br/tests/br_pitr/incremental_data/delete_range.sql.
2. Then print the content from mysql.gc_delete_range by select job_id, element_id, start_key, end_key from mysql.gc_delete_range.
3. Finally, use diff to check the result of the cluster based on the PR and the result of the cluster based on the master. They are the same.

• 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 assign ianthereal 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

[ti-chi-bot]

@ti-chi-bot: 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_2	876dc27	link	true	/test check-dev2
idc-jenkins-ci-tidb/build	876dc27	link	true	/test build
idc-jenkins-ci-tidb/unit-test	876dc27	link	true	/test unit-test
idc-jenkins-ci-tidb/mysql-test	876dc27	link	true	/test mysql-test
idc-jenkins-ci-tidb/check_dev	876dc27	link	true	/test check-dev

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