S3 bucket resources retry delete on conflicting conditional operation errors

[ewbankkit]

Description

Adds the missing AWS SDK for Go v2 retrier for the S3 service to handle OperationAborted: A conflicting conditional operation is currently in progress against this resource errors.

We have started to see this in CI tests:

=== RUN   TestAccS3Object_acl
=== PAUSE TestAccS3Object_acl
=== CONT  TestAccS3Object_acl
    testing_new.go:90: Error running post-test destroy, there may be dangling resources: exit status 1
        Error: deleting S3 Bucket Versioning (tf-acc-test-761094833802875805): operation error S3: PutBucketVersioning, https response error StatusCode: 409, RequestID: 67XZN6YTK82B46CQ, HostID: X3siXlSEfH6iGAErsiv/vWyRhUg4awkHQRpV4tsOH3fNvZtgZLhd6bToUlE4TflUXBiMXAja5TE=, api error OperationAborted: A conflicting conditional operation is currently in progress against this resource. Please try again.
--- FAIL: TestAccS3Object_acl (823.69s)

Relations

Closes #33478.
Relates #7628.
Relates #12949.

Output from Acceptance Testing

% make testacc TESTARGS='-run=TestAccS3BucketObject_acl' PKG=s3
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./internal/service/s3/... -v -count 1 -parallel 20  -run=TestAccS3BucketObject_acl -timeout 180m
=== RUN   TestAccS3BucketObject_acl
=== PAUSE TestAccS3BucketObject_acl
=== CONT  TestAccS3BucketObject_acl
--- PASS: TestAccS3BucketObject_acl (78.17s)
PASS
ok  	github.com/hashicorp/terraform-provider-aws/internal/service/s3	83.205s

[github-actions]

Community Note

Voting for Prioritization

• Please vote on this pull request by adding a 👍 reaction to the original post to help the community and maintainers prioritize this pull 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.

For Submitters

• Review the contribution guide relating to the type of change you are making to ensure all of the necessary steps have been taken.
• For new resources and data sources, use skaff to generate scaffolding with comments detailing common expectations.
• Whether or not the branch has been rebased will not impact prioritization, but doing so is always a welcome surprise.

[github-actions]

This functionality has been released in v5.18.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 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.