Build infrastructure for automatic management of zenodo records

Currently the problem is that someone updating the tutorial doesn't always have access to the zenodo record, maybe that person is gone.

So we should centralise the zenodo records under a "GTN account" that manages uploading.

I envision this as a folder of yaml files, with contents like "16s.yaml"

```
authors: hexylena, shiltemann # Pulled from CONTRIBUTORS.yaml, orcids mandatory
title: Some Library
description: |
blah
keywords:
- one
- two
- three
grants:
- 123572
```

all files from the similarly named `16s/*` would be uploaded into this zenodo record automatically.

We can easily detect when the yaml or files for a given 'record' changes, and update the zenodo record accordingly.

Using git instead of the zenodo interface means we can do more community management (e.g. normalising file extensions.)