Task Description (Required)

We're currently using ArgoCD's admin user to work with AI Rolling Demo and its default project.

Ideally we should be using an AI Rolling Demo specific user who has permissions only for the rolling-demo ArgoCD project.

This user should have permissions to create api_key.

Approach

• A new argoCD project (ai-rolling-demo) is created 
• A new user (ai-rolling-demo-user) has been created with access to ai-rolling-demo
• ai-rolling-demo-user has the permission to create api_key
• All the applications created via rolling demo should be assigned to the new project
• The ARGOCD_API_TOKEN key of argocd-secrets secret in rolling-demo-ns has been replaced with a new api key that has only access to the new project
• Same applies for argo cd password and user in argocd-secrets

Acceptance Criteria

• The rolling demo instance is operating on argocd's ai-rolling-demo-user and ai-rolling-demo project.