dxf: systable and scheduler change for modify task at runtime

[D3Hunter]

What problem does this PR solve?

Issue Number: ref #57497

Problem Summary:

What changed and how does it work?

Add a new task state modifying and add a new field modify_params which holds parameters about current modification. the system table change part has verified with PM @Frank945946
Add some basic interface in storage for modify and add a empty impl in scheduler

Check List

Tests

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

upgrade from 8.1, success, task and history table matches
bootstrap with master, success, task and history table matches

• 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 ask for approval from d3hunter and additionally assign benmeadowcroft, yujuncen 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:

• br/OWNERS
• pkg/disttask/OWNERS
• pkg/session/OWNERS

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

[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.

[codecov]

Codecov Report

Attention: Patch coverage is 72.72727% with 24 lines in your changes missing coverage. Please review.

Project coverage is 74.4630%. Comparing base (31c068c) to head (662094f).
Report is 15 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #57557        +/-   ##
================================================
+ Coverage   72.8799%   74.4630%   +1.5830%     
================================================
  Files          1676       1692        +16     
  Lines        463558     467397      +3839     
================================================
+ Hits         337841     348038     +10197     
+ Misses       104885      97806      -7079     
- Partials      20832      21553       +721     

Flag	Coverage Δ
integration	46.6539% <3.5714%> (?)
unit	72.1920% <75.2941%> (-0.0772%)	⬇️

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

Components	Coverage Δ
dumpling	52.7673% <ø> (+0.1129%)	⬆️
parser	∅ <ø> (∅)
br	60.5611% <ø> (+15.2075%)	⬆️

---- 🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests
• JS Bundle Analysis - Avoid shipping oversized bundles

[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.

[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.