Feature/integrate docker scout with git hub actions

[sinadarbouy]

Ticket(s)

Closes #510

Description

This PR introduces a new GitHub Actions workflow titled "Vulnerability Comparison." The workflow is designed to build a Docker image for each pull request and perform a vulnerability comparison using Docker Scout.
Additionally, this PR upgrades the Git version from 2.45.1-r0 to 2.45.2-r0 in the Dockerfile.

Git Version Upgrade

The Git version has been upgraded from 2.45.1-r0 to 2.45.2-r0. The previous version 2.45.1-r0 was not available in golang:1.22-alpine3.20, necessitating this upgrade.

Workflow Details

• Trigger: Runs on every pull request to any branch.
• Environment Variables:
  • IMAGE_NAME: The name of the Docker image repository (derived from the GitHub repository).
  • SHA: The SHA of the commit to build the Docker image from.
• Jobs:
  • vulnerability-comparison:
    • Runs on: ubuntu-latest
    • Permissions: Write access to pull requests
    • Steps:
      1. Checkout code: Checks out the code at the pull request's commit SHA.
      2. Set short SHA: Extracts a short version of the commit SHA for tagging the Docker image.
      3. Set up Docker Buildx: Prepares the environment for building Docker images using Buildx.
      4. Authenticate to Docker: Logs into Docker using credentials stored in GitHub Secrets.
      5. Build and push Docker image: Builds the Docker image and load it.
      6. Docker Scout Security Analysis: Compares the newly built image with the latest image in docker hub and reports vulnerabilities.

[sinadarbouy]

Docker Scout needs to authenticate with Docker Hub. The current step uses DOCKERHUB_USERNAME and DOCKERHUB_TOKEN, which I got them from the release workflow. but, it seems the vulnerability comparison workflow cannot access these secrets. @mostafa

[mostafa]

@sinadarbouy

Thanks for your contribution! 🙏