feat: create auto deployment workflow - [CU-869aqhbq2]

[LoayAhmed304]

Workflow

When a PR is MERGED into either dev or main:

1. Builds the Dockerfile (layers are cached)
2. Pushes new tag to the repository (Major or Minor depending on base branch)
3. Push to Dockerhub
   a. Push the newly created tag, and also push latest or staging-latest depending on environment
4. Send a discord message with the newly deployed status (and URL, staging or production)

Example of the Dockerhub repo

Example of the Repository tags

Eventually, there will be a watch tower on the machine that polls the manifests of the latest and staging-latest tags, pulls when a new hash is found and re-deploys. Docker composes and VM deployment files will be uploaded in a future PR.

The tags will be VERY important for the future rollback feature

[LoayAhmed304]

Task linked: CU-869aqhbq2 Build & Deploy Pipeline

[AhmedSobhy01]

Thanks to our DevOps leader