Create QAUserPool in Cognito replicating the DevUserPool (without users) to implement and test Cognito Advanced Security Features

Initial Background

Currently, all development and processes are being performed in the Dev Pipeline using the DevUserPool. Any changes made to the DevUserPool directly affect the development process and web application.

To safely test Cognito Advanced Security and Fraud Check features under implementation, a separate QAUserPool must be created as a replica of DevUserPool. This will isolate testing from development and ensure no disruption to ongoing work.

Expected Outcome

1. QAUserPool is created as a clone of DevUserPool (no users imported initially).
2. Proper routing and configurations are in place so test traffic can be directed to QAUserPool.
3. Logging is enabled in CloudWatch and CloudTrail to audit all actions related to QAUserPool.
4. Safe environment for testing Lambdas and fraud detection rules without impacting Dev or Prod.
5. Set up another webapp instance for QA with a corresponding URL - QA_saayam-netlify.app, which should replicate the current tested dev environment.

Acceptance Criteria

1. QAUserPool exists and mirrors DevUserPool configuration.
2. No existing users have been migrated to QAUserPool.
3. Both UserPools are isolated and don't affect each other.
4. CloudWatch logging is enabled for all Cognito Lambda triggers on QAUserPool.
5. CloudTrail events confirm visibility of all user pool modifications.
6. We want to remove any public buckets and have a QA bucket with the distinction: ex; Dev-private-virgina; qa-private-virginia; stage-private-virginia; prod-private-virginia; dev-private-ireland (x4) and the environment to be replicated are available to check on this section - https://github.com/saayam-for-all/devsecops/wiki/DevSecOps-CI-CD-Proposal (check the netlify app links to see the distinction)