✨ Use mri_robust_template for longitudinal template generation

[shnizzedy]

Related problem

Our implementation of longitudinal template generation gets stuck in a loop trying for convergence, whereas mri_robust_template works quickly.

Proposed feature

Add mri_robust_template as an option for longitudinal template generation OR replace our implementation entirely with mri_robust_template.

Acceptance criteria

C-PAC can use mri_robust_template for longitudinal workflow generation

Alternatives

No response

Additional context

• Related to hotfix-1.8.7/longitudinal by @shnizzedy
• Related to 🐛 No resources for warp_longitudinal_T1w_to_template #2159 by @Shinwon Park
• Related to Longitudinal project spec and longitudinal by @e-kenneally
• Related to Prepare longitudinal pipeline to be standalone #2133 by @sgiavasis
• Related to feature/nested_config_long by @XinhuiLi

[sgiavasis]

Our plans for the introduction of the longitudinal outputs into C-PAC's resource pool afterwards is the bigger question.
If you get mri_robust_template working, can we see the outputs it generates and ascertain when and how to use them in the subsequent pipeline/preprocessing?

We may need to update:

• C-PAC's ingress capabilities, and/or
• How C-PAC handles the logic of the minimal anat preproc that runs before longitudinal, how to handle forks, etc.
  • This can simply mean running C-PAC anat preproc first (and any forks the user may want), then running mri_robust_template and ingressing accordingly, I think?