lightning: move scan-split-scatter regions logic into common package

[lance6716]

What problem does this PR solve?

Issue Number: ref #51533

Problem Summary:

What changed and how does it work?

the split package now have a new method to scan, split and scatter region based on given sorted keys.

BR will use this new interface in next PR.

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

[tiprow]

Hi @lance6716. 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/test-infra repository.

[lance6716]

/ok-to-test

[lance6716]

/test pull-lightning-integration-test

[tiprow]

@lance6716: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

• /test fast_test_tiprow
• /test tidb_parser_test

Use /test all to run all jobs.

In response to this:

/test pull-lightning-integration-test

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.

[codecov]

Codecov Report

Merging #52399 (4b220c7) into master (29ced7f) will increase coverage by 0.2446%.
Report is 13 commits behind head on master.
The diff coverage is 82.3529%.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #52399        +/-   ##
================================================
+ Coverage   74.1411%   74.3858%   +0.2446%     
================================================
  Files          1467       1467                
  Lines        354227     428306     +74079     
================================================
+ Hits         262628     318599     +55971     
- Misses        72389      89838     +17449     
- Partials      19210      19869       +659     

Flag	Coverage Δ
integration	48.7813% <75.4902%> (?)
unit	71.0023% <67.6470%> (-1.8939%)	⬇️

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

Components	Coverage Δ
dumpling	53.9957% <ø> (-2.3014%)	⬇️
parser	∅ <ø> (∅)
br	49.7968% <81.6326%> (+7.3631%)	⬆️

[D3Hunter]

Suggested change

	util2 "github.com/pingcap/tidb/pkg/util"
	tidbutil "github.com/pingcap/tidb/pkg/util"

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-04-08 09:42:40.123132031 +0000 UTC m=+869021.650672574: ☑️ agreed by D3Hunter.
• 2024-04-09 02:06:31.508365611 +0000 UTC m=+928053.035906158: ☑️ agreed by tangenta.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: D3Hunter, tangenta, YuJuncen

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• br/OWNERS [YuJuncen]
• pkg/lightning/OWNERS [D3Hunter]

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