ddl, parser, executor, ddl worker: admin pause and resume ddl jobs

[dhysum]

What problem does this PR solve?
Issue Number: close #18015 #40041

Related issue number: #39751 #43061

Problem Summary:

• admin pause ddl jobs 3,5;
• admin resume ddl jobs 3,5;

pause an running DDL; and resume the paused DDL.

What is changed and how it works?

Once received the admin pause request, it will mark the Job as pausing, then the background worker will turn the DDL job to be paused and mark it as not processing. While, the admin resume is the contrary way.

cherry-pick from :

• parser and planner, ddl, parser, planner: admin Pause/Resume on DDL jobs #43081
• executor, ddl, executor: executor change for pause/resume on ddl jobs #43171
• background reorganization process, ddl: background reorganization change for admin pause/resume ... #43297
• design doc, ddl: design doc for admin pause/resume ddl jobs #43159

Check List

Tests

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

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.

- Support `admin pause ddl jobs 3,5;`
- Support `admin resume ddl jobs 3,5;`

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• Benjamin2037
• zimulala

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 submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[ti-chi-bot]

Hi @dhysum. Thanks for your PR.

I'm waiting for a pingcap member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

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.

[hawkingrei]

/ok-to-test

[dhysum]

/retest-required

[dhysum]

/retest

[Benjamin2037]

LGTM

[Benjamin2037]

/merge

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: 69a13e24b4e5d3addf30d5b5a77f00e6b104d4b1

[Benjamin2037]

/retest

[zimulala]

/merge

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: f606c0b

[dhysum]

/retest