create tutorial for model ingest

[alee]

• test on test.comses.net
• broadly cover software deposit guidance
• walkthrough entire deposit of codebase release
• discuss standard filesystem structure (could feed into a refactor as we look into look into SCIF #384)

Confusing parts of the interface:

• contributors improve contributor edit form #367
• image upload
• filesystem structure look into SCIF #384
• platform, languages, and other dependencies Build dependency editor for codebase release ingest Platform and Language #389
• publishing
• peer review
• DOIs

[alee]

As a first step / stopgap we need to add some clear guidance about the structure of the resulting file package that we will be building as people upload their models.

That is to say, whatever file is uploaded in the "Code" slot will be unzipped if it's a zipfile or tarball and placed in a <project-root>/code/ directory. Files uploaded to the data upload slot will be placed in <project-root>/data/. Likewise for docs in <project-root>/docs/.

So if the model author's code needs to reference some data uploaded in the data upload slot, it should use the relative filepath ../data/my-input-data.asc