Add S3 Replication KMS functionality

[ASTRobinson]

Key Changes
S3 Bucket Configuration:

• Defined and configured replication rules with KMS encryption.
• Enabled cross-account replication, ensuring that objects replicated to the destination bucket are encrypted using a customer-managed KMS key.
• Switch back v2 configuration, adding delete marker replication enabled (previously switched due to referencing out-of-date documentation.

IAM Role and Policy for Replication:

• Refactored IAM role with the required permissions to handle cross-account replication with KMS encryption.

KMS Key Configuration:

• Ensured that the destination bucket uses a customer-managed KMS key (moj-cur-reports-key) which is owned by the destination account for cross-account replication.

Replication Rules

• replica_kms_key_id - KMS key used for replicating objects
• metrics - Replication metrics are enabled for monitoring and troubleshooting.
• deletemarker - Enabled for versioned objects, ensuring that delete markers are replicated to the destination bucket.

[github-actions]

🦙 MegaLinter status: ✅ SUCCESS

Descriptor	Linter	Files	Fixed	Errors	Elapsed time
✅ REPOSITORY	gitleaks	yes		no	0.67s
✅ REPOSITORY	trivy	yes		no	14.48s
✅ TERRAFORM	terraform-fmt	4		0	0.23s
✅ TERRAFORM	tflint	yes		no	11.53s

See detailed report in MegaLinter reports
Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff

MegaLinter is graciously provided by

[connormaglynn]

🚀 Looks Good To Me!