Add Tutorial to User Guide as Appendix

[apcraig]

PR checklist

• Short (1 sentence) summary of your PR:
  Add Tutorial to User Guide as Appendix
• Developer(s):
  apcraig
• Suggest PR reviewers from list in the column to the right.
• Please copy the PR test results link or provide a summary of testing completed below.
  No testing done, only documentation changes, reviewed documentation via readthedocs
• How much do the PR code changes differ from the unmodified code?
  • bit for bit
  • different at roundoff level
  • more substantial
• Does this PR create or have dependencies on CICE or any other models?
  • Yes
  • No
• Does this PR add any new test cases?
  • Yes
  • No
• Is the documentation being updated? ("Documentation" includes information on the wiki or in the .rst files from doc/source/, which are used to create the online technical docs at https://readthedocs.org/projects/cice-consortium-cice/.)
  • Yes
  • No, does the documentation need to be updated at a later time?
    • Yes
    • No
• Please document the changes in detail, including why the changes are made. This will become part of the PR commit log.

Add the tutorial to the user guide as an appendix. Allows for easy links into the rest of the documentation and gives it a permanent and accessible home. The icepack variable name table was also moved to the new appendix section.

[dabail10]

Looks great!

[apcraig]

Should the appendices be after or before the references?

[dabail10]

Should the appendices be after or before the references?

I don't really have a preference.

[eclare108213]

These appendices make most sense before the references, in my opinion. This is awesome, thank you very much. I do (as usual) have quite a few little tweaky grammar kinds of things. I'll clone the branch...

[apcraig]

We could also get rid of the formal rst subsections (6.2.1, 6.2.2, etc) and just make those bolded (or similar) headings in the tutorial. That would remove them from the table of contents. I'm not sure they each deserve a separate rst section/heading.

[eclare108213]

I like how visible the subsections are in the text, and I don't mind them showing up in the table of contents.
I'm attempting to edit/commit directly in github. Let me know if you think that's a bad idea... seems like it will work.

[apcraig]

editing and committing in github is fine. individual commits are created just like if you did it in a sandbox.

[apcraig]

Everything looks good to me. Any other comments/changes?

[eclare108213]

This is great, thank you!