IntOGen-plus | build container improvement

[FedericaBrando]

We are updating the way containers are built.

Ideally we would like to automatize the developing process and the user-experience when installing the pipeline. Actions:

• [ ] add dockerfile recepies [Christian]
• [ ] add .gitworkflow to automatically checks build and push container [Christian]
• [x] specify each container dependancy version to use (pip packages and apt-get packages) [Fede]
• [x] decide a tagging strategy [Fede, Miguel]

FINAL GOAL: Let nextflow handle the pulling of containers and github action handle the pushing to registry whenever we have a new update

[FedericaBrando]

Regarding tagging strategy we decided the following as Christian advised:

we should name the containers with the intogen prefix, because they are not the official containers for the tools but something specific for intogen.

As an example, the project oncodriveFML should have its own CI/CD workflow that publishes a docker image, like oncodrivefml:1.0.2, then intogen-plus would build intogen-oncodrivefml:2.1.0 (note how the version correspond to the release version of each project) that looks like:

intogen-oncodrivefml/Dockerfile:
FROM bbglab/oncodrivefml:1.0.2
RUN ...