Describe your changes

What was supposed to be a quick change ended up being big. I created a module shmetrics, to give the possibility to compute metrics from SH files coming from anywhere. I added the option to used the msmt-fODF script in the frf and fodf modules. Also, I realised that frf and dtimetrics did not use scil_dwi_extract_shell.py at the beginning to ensure only DTI shells are used, so I added it to both, just as in fodf for the ssst method. In summary:

• Added a step to extract DTI shells in the reconst/dtimetrics module.
• Added a step to extract DTI shells in the reconst/frf module, in the case of single-shell method. Also, added the option of multi-shell method.
• Created a new reconst/shmetrics module to compute our typical metrics from whatever SH data, not only inside reconst/fodf.
• Added the option of multi-shell method to reconst/fodf.

For these four modules, all the tests were updated to the new way. Scilpy 2.0 is required so I also changed the container to scilus:2.0.0.

Say which test data are used by your module

This is complicated right now...

Checklist before requesting a review

• Create the tool:
  • Edit ./modules/nf-scil/<category>/<tool>/main.nf
  • Edit ./modules/nf-scil/<category>/<tool>/meta.yml
• Generate the tests:
  • Edit ./tests/modules/nf-scil/<category>/<tool>/main.nf
  • Edit ./tests/modules/nf-scil/<category>/<tool>/nextflow.config
  • Add test data locally for tests with the fork repository
  • Generate the test infrastructure and md5sum for all outputs
• Ensure the syntax is correct :
  • Check indentation abides with the rest of the library (don't hesitate to correct others !)
  • Lint everything. Ensure your variables have good names.