Fix/refine-tagging-logic

[Fovty]

Motivation

This PR addresses the issue of automatic "latest" tagging for main branch commits, which could mistakenly promote unstable builds into production. The update ensures that the "latest" tag is only applied to stable, versioned releases.

• Solves: Refine Docker Image Tagging Strategy to Enhance Stability in Releases #19

Changes

• Removed automatic "latest" tagging from main branch commits.
• "Latest" tag now only applies to new release tags.
• Added logic to extract version numbers from git tags for Docker image tagging.

TODO

• I've assigned myself to this PR.

[puffitos]

Looks great. You want to adress the deprecation in this PR or would you prefer to do that in a new PR?

Warning: The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

[Fovty]

I have addressed this small fix right here: 4192efa and fixed the new introduced bug here: 3031889. Now it should be fine

Looks great. You want to adress the deprecation in this PR or would you prefer to do that in a new PR?

Warning: The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

[puffitos]

Thanks for addressing the issues so quickly, well done 👏