feat(dms_endpoint): add DataFormat, EncryptionMode, and KmsKeyId to the S3 settings block

[doransmestad]

This pull request adds three new attributes to the S3 settings block of the dms_endpoint resource. This allows the user to specify S3 target endpoint in parquet format as well as specify the KMS key (or just server side sse-s3 encryption) to protect the exported data at rest.

Community Note

• Please vote on this pull request by adding a 👍 reaction to the original pull request comment to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for pull request followers and do not help prioritize the request

Release note for CHANGELOG:

Add `data_format`, `encryption_mode`, and `server_side_encryption_kms_key_id` to the S3 settings block of the aws_dms_endpoint resource.

Output from acceptance testing:

TF_ACC=1 go test ./... -v -count 1 -parallel 20 -run=TestAccAwsDmsEndpoint_S3 -timeout 120m
?   	github.com/terraform-providers/terraform-provider-aws	[no test files]
=== RUN   TestAccAwsDmsEndpoint_S3
=== PAUSE TestAccAwsDmsEndpoint_S3
=== RUN   TestAccAwsDmsEndpoint_S3Encrypted
=== PAUSE TestAccAwsDmsEndpoint_S3Encrypted
=== CONT  TestAccAwsDmsEndpoint_S3
=== CONT  TestAccAwsDmsEndpoint_S3Encrypted
--- PASS: TestAccAwsDmsEndpoint_S3 (143.29s)
--- PASS: TestAccAwsDmsEndpoint_S3Encrypted (252.60s)
PASS
ok  	github.com/terraform-providers/terraform-provider-aws/aws	252.696s

[YakDriver]

Related #14620
Related #17591
Related #18750

[anGie44]

Hi @doransmestad, thank you for this contribution and apologies for the delay. At this time, we've moved forward with #17591 which overlaps with the changes here. I'm going to close this PR as a result. But please keep a look out for this feature in the next provider release (v3.55.0).

[github-actions]

I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.