feat: add new data-source ses_domain_dkim

[stefanfreitag]

Rollback Plan

If a change needs to be reverted, we will publish an updated version of the library.

Changes to Security Controls

No changes to security controls are implemented.

Description

Add a new data source for accessing AWS SES Domain DKIM details.

Relations

Closes #44345

References

• Resource aws_ses_domain_dkim

Output from Acceptance Testing

❯ make testacc TESTS=TestAccSESDomainDKIMDataSource_basic PKG=ses
make: Verifying source code with gofmt...
==> Checking that code complies with gofmt requirements...
make: Running acceptance tests on branch: 🌿 f-aws-ses-domain-dkim 🌿...
TF_ACC=1 go1.24.8 test ./internal/service/ses/... -v -count 1 -parallel 20 -run='TestAccSESDomainDKIMDataSource_basic'  -timeout 360m -vet=off
2025/10/10 17:30:42 Creating Terraform AWS Provider (SDKv2-style)...
2025/10/10 17:30:42 Initializing Terraform AWS Provider (SDKv2-style)...
=== RUN   TestAccSESDomainDKIMDataSource_basic
=== PAUSE TestAccSESDomainDKIMDataSource_basic
=== CONT  TestAccSESDomainDKIMDataSource_basic
--- PASS: TestAccSESDomainDKIMDataSource_basic (30.26s)
PASS
ok      github.com/hashicorp/terraform-provider-aws/internal/service/ses        30.469s

[github-actions]

Community Guidelines

This comment is added to every new Pull Request to provide quick reference to how the Terraform AWS Provider is maintained. Please review the information below, and thank you for contributing to the community that keeps the provider thriving! 🚀

Voting for Prioritization

• Please vote on this Pull Request by adding a 👍 reaction to the original post to help the community and maintainers prioritize it.
• Please see our prioritization guide for additional information on how the maintainers handle prioritization.
• Please do not leave +1 or other comments that do not add relevant new information or questions; they generate extra noise for others following the Pull Request and do not help prioritize the request.

Pull Request Authors

• Review the contribution guide relating to the type of change you are making to ensure all of the necessary steps have been taken.
• Whether or not the branch has been rebased will not impact prioritization, but doing so is always a welcome surprise.