Consistent Version Tracking for Discourse Images

[cchaudier]

Description of the feature

Align Docker image tags so that each tiredofit/discourse tag accurately matches the Discourse version included in the image.
Currently, tiredofit/discourse:3.2.16 contains Discourse 3.4.7, which creates confusion and makes it difficult to deploy a specific Discourse version without checking the changelog.

Proposed tag structure:

• release-3.2.16 → internal container release version
• 3.4.7 → corresponding Discourse version
• 3.4.7+release-3.2.16 → combined reference tag

If a new patch release (release-3.2.17) still includes Discourse 3.4.7, the tag 3.4.7 should then point to 3.4.7+release-3.2.17.

Benefits of feature

• Provides clear, predictable version mapping between container releases and Discourse versions.
• Simplifies image selection for deployments without needing changelog cross-checking.
• Improves transparency and maintainability for users tracking specific Discourse versions.

Additional context

This change would require documenting the tagging convention in the README and verifying compatibility with the existing build and Docker Hub publishing workflow.
Add a badge with discourse version like

[cchaudier]

@tiredofit what did you think about my proposition ?