Motion correction option

[royj23]

• What is the current behaviour?

Motion correction is systematically applied to input scan, even if one uses an already pre-processed image (e.g. generated from fMRIprep, which applies motion correction already)

• What is the motivation / use case for changing the behaviour?

It is redundant to do motion correction twice in this case, but there is no way to skip this step in micapipe if running the pipeline through a container for example. Could the motion correction step be controlled via a yes/no flag? pretty please and many thanks