ddl: re-structure ddl executor part 2

[D3Hunter]

What problem does this PR solve?

Issue Number: ref #54436

Problem Summary:

What changed and how does it work?

executor.go is a large file, over 10K lines, it contains executor code, and also some code related to specific DDL execution, this pr separate them. we also separate the job submit part, and will abstract them into a job submitter as a separate struct

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No need to test: only move codes from one file to another

  • 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 @D3Hunter. 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.

[D3Hunter]

diff mess up, but we only move code anyway

[codecov]

Codecov Report

Attention: Patch coverage is 80.79357% with 789 lines in your changes missing coverage. Please review.

Project coverage is 75.7679%. Comparing base (da7ed5c) to head (957a140).
Report is 10 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #55140        +/-   ##
================================================
+ Coverage   74.8082%   75.7679%   +0.9596%     
================================================
  Files          1563       1569         +6     
  Lines        364342     445262     +80920     
================================================
+ Hits         272558     337366     +64808     
- Misses        72088      87164     +15076     
- Partials      19696      20732      +1036     

Flag	Coverage Δ
integration	51.4699% <63.6319%> (?)
unit	72.0569% <73.2229%> (-1.6401%)	⬇️

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

Components	Coverage Δ
dumpling	52.9567% <ø> (-2.2327%)	⬇️
parser	∅ <ø> (∅)
br	63.1288% <ø> (+15.4221%)	⬆️

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: lance6716, tangenta

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:

• pkg/ddl/OWNERS [tangenta]

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]

[LGTM Timeline notifier]

Timeline:

• 2024-08-02 03:21:35.97625413 +0000 UTC m=+59693.195015840: ☑️ agreed by lance6716.
• 2024-08-02 05:47:23.878249342 +0000 UTC m=+68441.097010950: ☑️ agreed by tangenta.

[D3Hunter]

/retest

[tiprow]

@D3Hunter: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

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.