The published images don't align with major/minor version tags, documentation advises otherwise

[mdaize-godaddy]

Describe the question/issue

The documentation (README.md) advises that major versions of the release should be available for use:

"3: The most recently released image version of the 3.x major version release."
Source: https://github.com/aws/aws-for-fluent-bit/tree/mainline?tab=readme-ov-file#aws-distro-for-fluent-bit-release-tags

It also seems that the image with that tag 3 does not show up here either: https://gallery.ecr.aws/aws-observability/aws-for-fluent-bit

Since the formal versioning advice is to lock to specific versions, it's our desire to use these immutable versions for major/minor version releases (source: https://github.com/aws/aws-for-fluent-bit/tree/mainline?tab=readme-ov-file#guidance-on-consuming-versions)

Note: We're okay with locking to either major or minor version (depending on the use case) and allow for such versions to automatically increment on release (eg. 3 allowing any minor version increment to 3.x, or 3.2 allowing any patch version increment to 3.2.x)

Steps to reproduce issue

Attempt to build the Dockerfile using the tag 3.

Desired solution

The major & minor version tags are made available to enable version locking in alignment with the documentation -- for example:

• 3 being the latest 3.x image release
• 3.2 being the latest 3.2.x image release