Revert "Make security policy stages order take precedence"
What does this MR do and why?
This reverts !141501 (merged).
As discussed this with Grant in a sync session we decided to not proceed with the stages precedence strategy in the pipeline execution experiment for now. I'm documenting all the strategies we came up with in the feature blueprint.
We already know this solution can mess up the project CI stages order. It will make CI harder to maintain for security and development teams, so we decided, if we know it won't work, we don't need to try it.
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.