Archival and DOI management for easyconfigs

[bmcgough]

• make eb put successfully built easyconfigs (including robo dependencies) into a separate folder
• link github repo to zenodo for auto archiving on release
• commit the separate easyconfigs, plus the 'sources' directory to repo

This gets us actual reproducibility as all the easyconfigs along with the sources will be in the repo (and then the archive with Zenodo).

[fizwit]

We still have not had any requests for DOI from users.

Rules of engagement:

• Do not built andy packages with --try
• Once a package is deployed it is to be considered immutable
• Do not remake any package name that is in use on EasyBuild master site
• Use fh1 (Fred Hutch X) version suffix when modifying an existing package
• Where possible use community build packages
• Contribute back new bioinformatics packages