Infrastructure: Move Staging ECS to EC2 & Shift Kaapi Instance to Kaapi VPC

[Ayush8923]

Describe the current behavior
Currently, the kaapi-backend staging and production both are deployed on the ECS. but for now we don't need a ECS for staging.

Describe the enhancement you'd like
So for this create the one EC2 Instance for the Backend staging and live the things there.

[Ayush8923]

Separate out the VPS for Kaapi:

• Use the AWS Secrets for the DB RDS Credentials, RabitMQ, redis cred. (Infra: Introduce AWS Secrets Manager #778)
• Rabit mq + Redis - another vhost for ec2-backend, redis DB.
• Move backend ec2 from dalgo VPC to kaapi staging VPC.
• Move Kaapi frontend and backend in Kaapi VPC, guardrails too.

[Ayush8923]

Separate out the VPS for Kaapi:

Move backend ec2 from dalgo VPC to kaapi staging VPC.

The staging instance are now live on the Kaapi VPC. On the frontend staging side, a new build needs to be created to sync everything up.

[Ayush8923]

Separate out the VPS for Kaapi:
Move backend ec2 from dalgo VPC to kaapi staging VPC.

The staging instance are now live on the Kaapi VPC. On the frontend staging side, a new build needs to be created to sync everything up.

The Production instances are now live on the Kaapi VPC. Also, all the features and bug fixes are live on production & staging instance.