Parallelize Push Latest Images Job

[bupd]

Summary

Currently, push-latest-images workflow job currently pushes images for all architectures sequentially in a single job. The "Publish and Sign Snapshot Image" step takes 1h 31m 19s to complete, making this one of
the slowest parts of our CI pipeline.

Proposed Solution

Refactor the push-latest-images job to use a GitHub Actions matrix strategy, where each architecture is built and pushed in parallel. This is similar to how many projects handle multi-arch builds.

Example structure:

push-latest-images:
    strategy:
      matrix:
        arch: [amd64, arm64, arm/v7]
    runs-on: ubuntu-latest
    steps:
      - name: Publish and Sign Snapshot Image
        # Push for ${{ matrix.arch }} only

After individual architecture images are pushed, a final job (dependent on the matrix job) would create and push the manifest list combining all architectures.

[nitishmalang]

@bupd can you please assign me this issue, i can work on it

[bupd]

we dont assign issues here @nitishmalang - please feel free to drop down your plan.

[Shivampal157]

hii @bupd , the plan I’m thinking

• Refactor the existing push-latest-images job to use a GitHub Actions matrix strategy,
  where each architecture (amd64, arm64, arm/v7) is built and pushed in parallel.
• Each matrix job will build and push its respective architecture-specific image.
• Add a final job that depends on the matrix jobs, which will create and push the
  multi-arch manifest combining all architectures.
• Ensure the behavior remains unchanged from a consumer perspective, while
  significantly reducing total CI runtime.

If this approach looks good, I can proceed with implementing it.