EB-179: Configure production and development Docker image builds

[RMCrean]

Hey :)

We have 5 workflows, 2 of which build images and the other 3 are more testing related.

For the 3 testing related I have set it up so that both a PR or push to main or prod triggers them to run.

For the 2 that build images I have now set it up so that:

• On PR no images are built.
• On push to prod, both images are built with tag "prod".
• On push to main both images are built with tag "dev".
• A workflow_dispatch (manual job) can be triggered to build either image on any branch (but not a fork). The default tag for the workflow dispatch will be "dev", but we have the choice to change that if we want when triggering the workflow.

I think this matches up with our plan. I've been testing out these settings using a personal repository and there it seems to be working nicely at least.

Related to this is of course the configuration of the branch settings, you can see those I have setup here: https://github.com/ScilifelabDataCentre/swedgene/settings/branches

Cheers!

[RMCrean]

P.S. I was looking into the creating new releases/tagging question. I think we could explore this GH action to make draft releases after each merge to prod. It looks very complete and is actively maintained.

[RMCrean]

Thanks @kwentine I will merge now even if we have some non-blocking comments/ideas still going so I can finish off work on the rename of the repo. :)