[Feature][Master Worker-Server] Global Param passed by sense dependencies

[wangxj3]

the param of task requires optimization,Need according to the dependency relationship between the nodes pass a variable's value, different depend on the chain of nodes before there is the same but different meanings, parameters can be distinguished from processInstance. GlobalParam, taskInstance. LocalParam

[github-actions]

Hi:

• Thank you for your feedback, we have received your issue, Please wait patiently for a reply.
• In order for us to understand your request as soon as possible, please provide detailed information、version or pictures.
• If you haven't received a reply for a long time, you can subscribe to the developer's email，Mail subscription steps reference https://dolphinscheduler.apache.org/zh-cn/community/development/subscribe.html ,Then write the issue URL in the email content and send question to dev@dolphinscheduler.apache.org.

[ruanwenjun]

1. Can we determine the value of param1 in Task2's varpool ? It may come from Task1 or generate by Task2
   
2. Can we determine the value of param1 in Task4's varpool?
   
3. The varpool might be huge in the back task, and they save the same data.
   

Suggestion

This is my personal opinion, for reference only.

[wangxj3]

thanks for you suggestion.
1.The Direct of the params that generate in the Task2 is OUT,and the Direct the params that get form the Task1 is IN.So we can determine the source of this value by the Direct of the params.I think this is the same way with your suggestion.
2.When the previous tasks have the same param name,we will use the value which is't null.If more than two values are non-null,we will use the value that the earliest task's varpool.
3.This is the question of this plan ,We will optimize this issue in the future
So far I have finished coding,and will It will be submitted in a few days

[CalvinKirs]

close by #5603