Use 'latest' docker tag for stable releases only

[corverroos]

Problem to be solved

Currently, we are using the latest Docker tag to represent both stable and unstable builds from our main branch. This is counter to the common practice in Docker workflows, where the latest tag is usually reserved for the most recent stable release. This current usage can potentially confuse users and lead to inadvertent use of unstable builds when a stable build is expected.

Proposed solution

To resolve this issue, we propose adjusting our Docker tagging strategy as follows:

• Use the latest tag only for the latest stable releases. This follows common Docker practices and will make it clear for users that they are getting a stable version of the software.

• Continue using specific version tags (e.g., v0.X) for each stable release to allow users to pull specific versions if required.

• Introduce a new Docker tag (e.g., next, unstable, dev) for the most recent main branch commits. This will provide an option for users who wish to use or test the latest changes in our software, even if these changes haven't been officially released.

By implementing this tagging strategy, we can provide clear expectations about the stability and freshness of the software represented by each Docker image.

---

[corverroos]

Poll indicates we should use the dev tag since it matches the current v0.X-dev tag we already add to main branch commits