Rudder

To implement #12194, we need to do modification in Rudder core because we need to be able to decide, given a change request, if that change must be validated with one or another workflow.

This goes above what was firstly imagined of being able to just let the workflow decide what to do (i.e: always use the same workflow, but depending on the change, let it be auto-validated or not), because we need to know early (before workflow start) if the change will need validation or not because we want to inform the user in the validation pop-up (before save).

Most Workflow engines don't work like ours for that exact reason. As steps are not known statically, you can't know what to write before running the workflow. It seems to be a better, more generalized solution, but I don't know how to do that without massive change in Rudder.