s3(control): Complete migration to AWS SDK for Go v2

[ewbankkit]

Complete the migration of the S3 and S3 Control resources and data sources to AWS SDK for Go v2.
The following are blocked from migration pending resolution of aws/aws-sdk-go-v2#2162:

• aws_s3_account_public_access_block resource and data source
• aws_s3_bucket resource
• aws_s3_bucket_public_access_block resource
• aws_s3_bucket_lifecycle_configuration resource
• aws_s3_bucket_replication_configuration resource

Relates #33593.
Relates #33537.
Relates #33431.
Relates #33358.
Relates #33330.
Relates #33304.
Relates #33416.
Relates aws/aws-sdk-go-v2#2384.

aws_s3_bucket_lifecycle_configuration and aws_s3_bucket_replication_configuration can be be migrated by reverting 47f1924.

[github-actions]

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please see our prioritization guide for information on how we prioritize.
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.

[ewbankkit]

s3control should now be fully migratable -- aws/aws-sdk-go-v2#2333, #34096.

[ewbankkit]

Also s3 -- https://github.com/aws/aws-sdk-go-v2/releases/tag/release-2023-11-17.

[ewbankkit]

Just aws_s3_bucket remains -- will tackle after re:Invent.

[github-actions]

This functionality has been released in v5.32.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

[github-actions]

I'm going to lock this issue 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 similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.