Create proper conda releases for MicadoWISE

We should create proper conda releases for MicadoWISE.

Currently we do not yet create any releases for MicadoWISE. We only build it automatically through the conda-build.yml ci template, but do not upload it. Installation therefore requires building MicadoWISE, instead of just doing conda install micadowise. This was fine up till now because the only people using MicadoWISE were its developers. Now MicadoWISE is stable enough that it can be used by others, e.g. the MPE team.

Proposal is to follow the same scheme as astro:

• Reintroduce the develop branch as default branch, and use the master branch for releases.
• Set proper versions (check in astro where).
• Merge monthly into master through monthlymerge.yml ci template.
• Release through conda-release.yml ci template (imported through conda.yml).
• Create monthly CI job.
• Release to omegacen anaconda channel as well.
• Also release the environment.yml
• Perhaps do not run CI on master but only on tags? Since they run together they might get killed.

Improve documentation:

• Add that it might be necessary to restart jobs if they get killed.
• How to update Peregrine / Jupyter hub.
• How to do data model evolution.
• Add link to anaconda channel.
• Optionally send email with announcement.