Use Terragrunt for dynamic backends (github actions)

[npeterson54]

Description

We will leverage Terragrunt's dynamic backends for this, and state will be kept within AWS S3.

Notes

• Every cluster deployed must have it's very own state file

Resources

• https://terragrunt.gruntwork.io/docs/features/keep-your-remote-state-configuration-dry/
• https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/s3_bucket

Acceptance Criteria

• [x] Create a new S3 bucket where all cluster state files will be kept
• [x] The S3 bucket [and associated resources] should be managed via terraform and kept within the vsp-platform-infrastructure repo

Refinement Guidance - Check the following before working on this issue:

• [x] Team label assigned ("platform-tech-team-2")
• [x] Epic assigned (if needed)
• [x] Estimated (points assigned)
• [ ] Sprint assigned (once planned)
• [ ] Team member(s) assigned

[it-harrison]

looks good!