feat(core): restarting Subflow

[loicmathieu]

When restarting an execution, each Subflow and ForEachItem tasks will restart failing subflow executions instead of creating a new one. This behavior is manageable via the new restartBehavior property, configuring to NEW_EXECUTION will create new executions as before. If the subflow executions was in SUCCESS, it will not be restarted nor a new execution will be created, this is important for ForEachItem.

Fixes https://github.com/kestra-io/kestra-ee/issues/1399

Two changes:

• When restarting an execution, a system label is added so we know from the Subflow or ForEachItem task that we need to restart the child execution: system.restarted: true.
• Inside the subflow execution, the execution trigger variables have been enhanced with taskRun ID and taskRun value and taskRun iteration so we can find the correct execution to restart in case the Subflow is inside a ForEach
  

[sonarqubecloud]

Quality Gate passed

Issues
9 New issues
0 Accepted issues

Measures
0 Security Hotspots
85.5% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[loicmathieu]

Breaking Change

When restarting an execution, Subflowor ForEachItem tasks will restart the existing failed subflow instead of creating new ones.
This behavior is manageable via a new restartBehavior property, configure it to NEW_EXECUTION to go back to the previous behavior of creating new subflow executions on restart.