UI to support starting a job from workflowgraph without inheriting the context from the current event

[sagar1312]

What happened:

In the current UI, both "Restart pipeline from here" and "Start pipeline from here" always inherits the context from the current event.

• Parameters are copied from current event to the new event
• meta of current event is to the new event which acts as the base for all the builds in the new event
• Current event is set as the parent event for the new event
• Current event and the new event are also associated to the same event group

There is no way to start a new event (unless it is started from the ~commit trigger) without inheriting the context from the current event.
This may lead to confusion and undesired result especially for detached jobs when the user clicks "Start pipeline from here". The user may assume that the newly created event does not inherit any context from the current event.

What you expected to happen:
There should be an option for the user to start a new event without inheriting the context from the current event in the workflow graph.

• "Restart event from here" would start a new event by inheriting the context from the current event
• "Start a new event from here" would start a new event without inheriting the context from current event

How to reproduce it:
Sample pipeline config: https://github.com/sagar1312/screwdriver-config/blob/main/detached-jobs/screwdriver.yaml

Sample pipeline: https://cd.screwdriver.cd/v2/pipelines/15906/events/835435