Add/finish templates for m-file user documentation to Advisor class

[rtopfer]

To standardize and facilitate documenting new .m files, templates should be made available.
I.e. Standard formating for help section of scripts, functions, classes + class members.

e.g. Should there be standard sections such as

Summary

Inputs

References

Etc.

[jcohenadad]

Related to

• Update Travis build with correct pip install for shimming-toolbox shimming-toolbox#145
• Change to a decorator in test_dicom_to_nifti shimming-toolbox#133

[jcohenadad]

Started something here. I know it's somewhat a duplicate of function_template.m, but it has the merit of being a "real-life" example.

My first question would be: can we replace __FIELD__ by FIELD? I assume it would be as easily parsed, and looks better when calling the help in the command window. @rtopfer? @po09i?

[rtopfer]

can we replace FIELD by FIELD?

yes, easily done using replace

on another note, I'm still in favour of not including authorship in the doc header (except, of course, when the file has been taken from somewhere else). it doesn't strike me as particularly useful and encourages contact via email rather than through GitHub issues.

[jcohenadad]

Related to: shimming-toolbox/shimming-toolbox#133