Feature/push to docker hub

[Topin2001]

Proposed changes

The idea is to deploy the docker image into docker hub, when a new release is created

Types of changes

What types of changes does your code introduce to this project?

Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• [ x] New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices apply)

Issues closed by changes

List here all issues closed by your changes. Use a list of items like - [x] Close #0

• Close #0

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• [x ] I have read the CONTRIBUTING doc
• [ x] I agree with the CODE OF CONDUCT
• Lint and unit tests pass locally with my changes
• Codacy validates the quality of the modifications
• [x ] GitHub Actions CI workflow passes
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)
• Any dependent changes have been merged and published in downstream modules

[louisjdmartin]

Une bonne pratique est d'éviter les "latest" dans une intégration continue, cela permet d'avoir des CI reproductible, on va préférer figer une version (a minima, figer la version majeure pour bénificer des patchs de sécu tout de même)

Si besoin d'un ubuntu plus récent, tu peux mettre ubuntu-22.04 ou 23.10. ubuntu a de plus une sacré tendance a casser plein de trucs d'une version majeure a l'autre :)

[gbonnefille]

@Topin2001 did you plan to do the same thing on https://github.com/cnescatlab/sonarqube and https://github.com/cnescatlab/sonar-scanner?

I opened an issue cnescatlab/sonarqube-catlab#40 and started a PR cnescatlab/sonarqube-catlab#41