refactor addTask method argument order
To streamline the API, the order of the method arguments in ->addTask should be changed.
First argument should be the stage.
Maybe we still can make it backwards compatible by checking, if the first argument is a valid stage name in the given workflow. If not the first and second argument should be swapped (and a deprecation warning should be logged)
No data to display