feat: Enhance Release and Docker deploy CD

[Quentinchampenois]

Describe the bug
A clear and concise description of what the bug is.

At the moment release version is automatic based on conventional commits in history. With this system we cannot choose the next release version except by manually publish a new one.

We should refactor the CD pipeline to build the final Docker image on Release publication hook. This way, we could be able to choose by adding a tag release: v2.6.2 and if the tag is present and also target branch is master, then it publishes the new release.

Resources

• Release events
• Label tag version GH Action