Add ability to fix pipeline flow to identify if no code change is necessary
Problem
As brought up in !3256 (comment 2728055050) there are cases where a pipeline is just flaky or failing e.g. due to an external resource not being available. There could also be other changes outside of the immediate MR that are responsible for the failing pipeline.
In these cases there is no code change necessary.
Desired Outcome
Flow can identify cases where no code change to current MR is necessary and provide a summary and potentially different solution (e.g. rebase/retry pipeline)
Proposed Solution TBD
Edited by Sebastian Rehm