Add auto-retry limit support for CodeBuild

[rayennh]

Description

This pull request adds the auto_retry_limit argument to the aws_codebuild_project resource. This new setting allows users to specify the number of automatic retry attempts for a CodeBuild project.

Relations

Closes #39921

References

Output from Acceptance Testing

$ make testacc TESTS=TestAccCodeBuildProject_autoRetryLimit PKG=codebuild

make: Verifying source code with gofmt...
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go1.23.2 test ./internal/service/codebuild/... -v -count 1 -parallel 20 -run='TestAccCodeBuildProject_autoRetryLimit'  -timeout 360m
2024/11/08 13:44:56 Initializing Terraform AWS Provider...
=== RUN   TestAccCodeBuildProject_autoRetryLimit
=== PAUSE TestAccCodeBuildProject_autoRetryLimit
=== CONT  TestAccCodeBuildProject_autoRetryLimit
--- PASS: TestAccCodeBuildProject_autoRetryLimit (51.82s)
PASS
ok      github.com/hashicorp/terraform-provider-aws/internal/service/codebuild  55.902s

[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]

Welcome @rayennh 👋

It looks like this is your first Pull Request submission to the Terraform AWS Provider! If you haven’t already done so please make sure you have checked out our CONTRIBUTOR guide and FAQ to make sure your contribution is adhering to best practice and has all the necessary elements in place for a successful approval.

Also take a look at our FAQ which details how we prioritize Pull Requests for inclusion.

Thanks again, and welcome to the community! 😃