ci: rework tag and labels for Docker CI Build

[psyray]

This PR fix the Docker images CI build which not correctly set Arch leading to problem during install (manifest file not found).

1. Removal of the platform matrix since we'll handle both architectures in a single build step

2. Addition of the Docker meta step to manage tags and labels:

   • Configuration of tags for branches, PRs, semantic versions and SHA
   • Using a prefix rengine-${{ matrix.image }}- for each image
   • Tags will be automatically generated according to context (branch, tag, PR)

3. Modification of the Build and push step:

   • Using tags and labels generated by metadata-action
   • Configuration of both platforms in a single step with platforms: linux/amd64,linux/arm64

This configuration should solve your issue because:

• Tags will be managed consistently across all architectures
• Multi-architecture build will be done in a single step
• Metadata will be correctly applied to all architecture variants

The resulting images will have tags like:

• rengine-web-v2.1.0
• rengine-web-latest
• rengine-web-2.1
• rengine-web-2

And each tag will properly support both architectures (amd64 and arm64).

This configuration will also allow:

1. On a release/X.Y.Z branch:

   • Semantic tags will be generated (X.Y.Z, X.Y)
   • No latest tag

2. On the master branch:

   • The latest tag will be generated
   • Images will be tagged with the branch name

3. During a workflow_dispatch:

   • On a release/* branch: version tags generation only
   • On master: latest tag generation
   • On other branches: tag with branch name

Thus, the latest tag remains exclusive to master, while still allowing appropriate version tags to be generated from release branches.

Summary by Sourcery

CI:

• Rework Docker CI build to handle both amd64 and arm64 architectures in a single build step, removing the platform matrix.

[sourcery-ai]

Hey @psyray - I've reviewed your changes - here's some feedback:

Overall Comments:

• Please add documentation explaining why BUILDX_NO_DEFAULT_ATTESTATIONS is being disabled and what impact this has on the build process. This context is important for future maintainers.

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟡 Security: 1 issue found
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[psyray]

@sourcery-ai review

[sourcery-ai]

Reviewer's Guide by Sourcery

The PR updates the Docker CI build workflow by replacing manual version tagging with the docker/metadata-action and modifying how platform targets are specified.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change	Details	Files
Replace manual version tagging with docker/metadata-action	Remove manual version extraction from git refs Add docker/metadata-action with comprehensive tag patterns for branches, PRs, semver, and latest Configure image prefix and tag formatting using metadata action's flavor option	.github/workflows/build.yml
Streamline Docker build platform configuration	Remove platform matrix configuration Directly specify platforms in build step Add labels output from metadata action to build configuration	.github/workflows/build.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time. You can also use
  this command to specify where the summary should be inserted.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey @psyray - I've reviewed your changes - here's some feedback:

Overall Comments:

• The BUILDX_NO_DEFAULT_ATTESTATIONS environment variable mentioned in the description is not implemented in the workflow file. Please add it if it's intended to be part of this change.

Here's what I looked at during the review

• 🟢 General issues: all looks good
• 🟢 Security: all looks good
• 🟢 Testing: all looks good
• 🟢 Complexity: all looks good
• 🟢 Documentation: all looks good

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}