ddl: support pre-split index regions before creating index (#57553)

[ti-chi-bot]

This is an automated cherry-pick of #57553

What problem does this PR solve?

Issue Number: close #57552, close #57551

Problem Summary:

See #57552.

What changed and how does it work?

• Support specifying the split option in the index option at parser.
• Split the target index region by keys or ranges before data reorganization when adding an index.
• Extract common code and tests from pkg/executor/split.go to pkg/util/split.go.
• Add two functional tests.

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

[codecov]

Codecov Report

Attention: Patch coverage is 26.04651% with 318 lines in your changes missing coverage. Please review.

Please upload report for BASE (release-7.5@738a65b). Learn more about missing BASE report.

Additional details and impacted files

@@               Coverage Diff                @@
##             release-7.5     #58541   +/-   ##
================================================
  Coverage               ?   72.0891%           
================================================
  Files                  ?       1419           
  Lines                  ?     413699           
  Branches               ?          0           
================================================
  Hits                   ?     298232           
  Misses                 ?      95447           
  Partials               ?      20020           

Flag	Coverage Δ
unit	72.0891% <26.0465%> (?)

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

Components	Coverage Δ
dumpling	52.9400% <0.0000%> (?)
parser	∅ <0.0000%> (?)
br	53.5087% <0.0000%> (?)

[tangenta]

/retest

[tangenta]

/retest

[tangenta]

/retest

[ti-chi-bot]

@benmeadowcroft: adding LGTM is restricted to approvers and reviewers in OWNERS files.

In response to this:

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.

[Benjamin2037]

LGTM

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2025-02-27 08:56:52.027971691 +0000 UTC m=+518959.981129958: ☑️ agreed by Benjamin2037.
• 2025-02-28 06:26:11.141007295 +0000 UTC m=+596319.094165562: ☑️ agreed by fzzf678.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Benjamin2037, benmeadowcroft, fzzf678, tangenta
Once this PR has been reviewed and has the lgtm label, please ask for approval from tangenta and additionally assign d3hunter, easonn7 for approval(Please 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 [Benjamin2037,tangenta]
• pkg/ddl/OWNERS [Benjamin2037,tangenta]
• pkg/parser/OWNERS [tangenta]

  Need more approvers for rest parts.

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