Setup argo cd pipeline for auto deployment

[vishnoianil]

We need to setup two Argo CD pipelines :

1. QA Deployment : Whenever any new code is merged in the main branch, it should be deployed in the qa.ui.instructlab.ai. Merge of the PR generates both UI and path service images and push it to quay.io and ghcr.io with main tag.

2. Whenever any new release is created from release-* branch (e.g release-1.0) it should be auto deployed in the ui.instructlab.ai. New release is created using a new tag (and not a branch) (e.g v1.0.0-beta.2). Once the new release is create, it will generate images and push it to quay.io and ghcr.io with the same image tag as release tag, also it creates latest tag for the same images.

Notes:

• In both the scenarios, restarting the pods should pull the latest image from the quay.io and deploy it.
• Both the deployments depends on it's own set of environment variables. These environment variables need to be stored as encrypted secrets that is accessible by argo CD pipelines.
• Also we can automate the the production deployment for ui.instructlab.ai, but having an option to manually trigger the production deployment can be helpful in multiple scenarios (hot patching).

[vishnoianil]

@Gregory-Pereira I assume most of the task are complete it (except the auto trigger part).

[vishnoianil]

@Gregory-Pereira I believe this is done? is this tested for the production update?

[Gregory-Pereira]

I have not tested prod yet but everything is done. I will be making the testing releases today