[Feature]Blocking task UI and Doc

[mgsky1]

Purpose of the pull request

This PR adds blocking task UI and documentation. The blocking task node backed code has been merged in PR #6272.

Brief change log

• add blocking task icon
• add blocking task configuration pannel
• add operations (continue or re-run) when the workflow has been blocked
• add blocking task documentation in Chinese and English

Screen Shots

Verify this pull request

Test cases:

• normal: i.e. Blocking node has upstream and downstram nodes.
• blocking node in the begining of workflow.
• blocking node in the end of workflow.

They all work fine.

Discuss

• When config blocking node, it has a alert option. In my view, it is better to use switch plugin, but I do not know how to set switch plugin value when the switch turning on or off.
• As for the operation after the workflow is blocked. I think re-run and continue execution is rational. When I testing the operation: continuing from faild node, this operation will skip those node which has been executed successfully. It means that blocking node will lose its function. So I disable this operation.

---

此PR的目的

为了完善阻断类任务的开发，后端代码已经在PR#6272中被合并

变更日志

• 阻断类任务图标
• 阻断节点配置面板
• 当工作流被阻断时，提供重跑和继续执行，两种选择
• 增加阻断节点中英文档

截图

测试

主要测试了以下几种情况

• 正常模式：阻断节点上下游都有任务
• 阻断节点在工作流头部（没有上游节点）
• 阻断节点在工作流尾部（没有下游节点）

它们都能正常工作

讨论

• 在阻断节点的配置中，有一个告警选项，我觉得将其作为switch开关更合适，但是我不知道如何给这个switch开关赋值，从代码来看，新的ui将配置项的每一条都抽出进行了高度封装，返回IJsonItem数组，不知道这种场景下，要用IJsonItem的什么字段给开关赋值。从现有的代码参考看，如果是在节点配置面板中使用了switch开关，那么开启开关后，会弹出更详细的设置信息；另外一处是在工作流空跑时出现的，那个场景是直接用HTML标签搞定的。
• 对于工作流被阻断后的操作，我觉得继续执行和重跑是合理的。对于重新执行失败节点，在测试中发现，这种模式会跳过已经执行成功的节点，这会导致阻断节点的失效，因此不启用。

[SbloodyS]

That's a cool~

[codecov-commenter]

Codecov Report

Merging #10397 (87613d6) into dev (6d8befa) will decrease coverage by 0.16%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##                dev   #10397      +/-   ##
============================================
- Coverage     39.46%   39.29%   -0.17%     
  Complexity     4247     4247              
============================================
  Files          1052     1061       +9     
  Lines         39860    40050     +190     
  Branches       4582     4600      +18     
============================================
+ Hits          15731    15739       +8     
- Misses        22349    22530     +181     
- Partials       1780     1781       +1     

Impacted Files	Coverage Δ
...cheduler/api/service/impl/ExecutorServiceImpl.java	43.73% <0.00%> (ø)
...rver/master/runner/task/BlockingTaskProcessor.java	76.40% <0.00%> (ø)
...plugin/task/api/parameters/BlockingParameters.java	0.00% <ø> (ø)
...erver/master/processor/queue/TaskEventService.java	69.64% <0.00%> (-10.72%)	⬇️
...r/plugin/registry/zookeeper/ZookeeperRegistry.java	43.54% <0.00%> (-6.46%)	⬇️
...lphinscheduler/plugin/kubeflow/KubeflowHelper.java	81.39% <0.00%> (-5.45%)	⬇️
...dolphinscheduler/remote/future/ResponseFuture.java	81.96% <0.00%> (-1.64%)	⬇️
...r/plugin/task/sqoop/parameter/SqoopParameters.java	51.19% <0.00%> (-1.20%)	⬇️
...eduler/api/service/impl/DataSourceServiceImpl.java	50.75% <0.00%> (-1.02%)	⬇️
...che/dolphinscheduler/alert/AlertSenderService.java	45.39% <0.00%> (-0.61%)	⬇️
... and 15 more

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[sonarqubecloud]

SonarCloud Quality Gate failed.   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

0.0% Coverage
0.0% Duplication

[zhongjiajie]

backend and docs LGTM, @devosend please task a look at the frontend code

[zhongjiajie]

It seems that is unnecessary adding

[zhongjiajie]

should avoid using number in title, the leading number of # represent the level

Suggested change

	### 1. Create Workflow
	### Create Workflow

[mgsky1]

I am very very sorry for updating this PR so late because of the busy work and training. I see projects iterating rapidly and the back-end code for the blocking node is still being maintained. I sincerely appreciated.
@zhongjiajie @caishunfeng

[EricGao888]

I am very very sorry for updating this PR so late because of the busy work and training. I see projects iterating rapidly and the back-end code for the blocking node is still being maintained. I sincerely appreciated. @zhongjiajie @caishunfeng

@mgsky1 No worries, we are glad that you could follow up with this PR. The CI failed because of formatting errors, could u plz run mvn spotless:apply under the root directory so that spotless will automatically fix those errors for you?

[mgsky1]

I am very very sorry for updating this PR so late because of the busy work and training. I see projects iterating rapidly and the back-end code for the blocking node is still being maintained. I sincerely appreciated. @zhongjiajie @caishunfeng

@mgsky1 No worries, we are glad that you could follow up with this PR. The CI failed because of formatting errors, could u plz run mvn spotless:apply under the root directory so that spotless will automatically fix those errors for you?

ok，I will run this command later today~

[mgsky1]

There are still some errors occured in the Actions. I will fixed them later, maybe in this weekend

[sonarqubecloud]

SonarCloud Quality Gate failed.   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

0.0% Coverage
0.4% Duplication

[mgsky1]

I fixed some error in code so that the Actions could be executed. I also clean the commits. The commit logs before are so terrible.@EricGao888

[caishunfeng]

Hi @mgsky1 It's great to follow up the blocking task feature 👍
Please resolve the conflicts.

[caishunfeng]

@devosend @Amy0104 @songjianet Do you have time to review this pr?

[devosend]

frontend LGTM

[songjianet]

Please resolve the conflict. @mgsky1

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity for 120 days. It will be closed in 7 days if no further activity occurs.

[github-actions]

This pull request has been closed because it has not had recent activity. You could reopen it if you try to continue your work, and anyone who are interested in it are encouraged to continue work on this pull request.