Strapi instance in Cloud.gov

## Tasks
- [x] Establish a bashscript to bootstrap CloudFoundry for Terraform resources
- [x] Establish terraform module for RDS/Database config
- [x] Establish terraform module for Strapi Deployment
- [x] Test Cloud.gov OAuth as an IDP with Strapi

## Acceptance Criteria
- [x] Strapi instance is configured and accessible as a Dev environment with Cloud.gov

## Definition of Done

- Acceptance criteria met - Acceptance criteria should answer the question “How will the Product Owner validate that the user story works?”
- Code refactored for clarity - Code must be clean and concise and not require comments to be understood
- Dependency Rule followed - Higher-level code should not depend directly on lower-level code
- Source code merged - Code that is reviewed and tested must be in source control and merged into the master.
- Unit test coverage of our code = 90% - Automated test coverage tools indicate code coverage of 90% or more.
- Code reviewed - Code reviewed by at least two team members (one, if developed by a pair).
- Security reviewed and reported - Vulnerability and compliance scanning completed, if needed. Defense measures to protect data, authentication and authorization are evaluated. Infrastructure configurations evaluated for vulnerabilities.
- Critical issues resolved. Non critical issues are added to the product backlog.
- No local design debt - User story can be built, tested and deployed without local developer workstation dependency.
- Build process updated - Build process is updated as required and includes implementation of automated code analysis (Sonar, linters, etc.).
- Code quality checks passed - Code build passes all automated quality checks.
- Accessibility tests passed - Accessibility testing completed. Critical issues resolved. Non critical issues are added to the product backlog.
- Guides and training draft created - Guides and training material are created and placed under version control.
- Feature toggles created - For features that require implementation flexibility, feature toggles are created and verified.
- Developer documentation generated - API and other documentation needed for developers to effectively use the code is created and placed under version control.
- Public announcements created - Release documentation, website blogs, etc. are created, published and placed under version control.
- Security and privacy gates passed - A formal security or privacy authorization to operate

Review the bash bootstrap script and Terraform modules for RDS/database and Strapi deployment named in the issue. Start by checking the Cloud.gov environment and OAuth/Strapi configuration; done would be a reachable Dev Strapi instance with the listed acceptance and quality gates satisfied.

Written by the indexing model from the issue text.