feat: Add skip_resource_in_use_check arg to aws_bedrockagent_agent

[acwwat]

Description

This PR is to add the skip_resource_in_use_check argument to the aws_bedrockagent_agent resource, so that there is an option to get past the validation error if the agent still has aliases before its deletion. Note that the this is not a standard parameter in the Agent API object, but it is an attribute to pass along to the DeleteAgent API.

Relations

Closes #37161

References

Referred to DeleteAgent for spec and aws_bedrockagent_agent_action_group resource doc for wordings (the AWS API ref description is too verbose).

Output from Acceptance Testing

$ make testacc TESTS=TestAccBedrockAgentAgent_ PKG=bedrockagent
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go1.22.2 test ./internal/service/bedrockagent/... -v -count 1 -parallel 20 -run='TestAccBedrockAgentAgent_'  -timeout 360m
=== RUN   TestAccBedrockAgentAgent_basic
=== PAUSE TestAccBedrockAgentAgent_basic
=== RUN   TestAccBedrockAgentAgent_full
=== PAUSE TestAccBedrockAgentAgent_full
=== RUN   TestAccBedrockAgentAgent_update
=== PAUSE TestAccBedrockAgentAgent_update
=== RUN   TestAccBedrockAgentAgent_tags
=== PAUSE TestAccBedrockAgentAgent_tags
=== CONT  TestAccBedrockAgentAgent_basic
=== CONT  TestAccBedrockAgentAgent_update
=== CONT  TestAccBedrockAgentAgent_full
=== CONT  TestAccBedrockAgentAgent_tags
--- PASS: TestAccBedrockAgentAgent_basic (25.19s)
--- PASS: TestAccBedrockAgentAgent_full (25.57s)
--- PASS: TestAccBedrockAgentAgent_tags (47.61s)
--- PASS: TestAccBedrockAgentAgent_update (50.76s)
PASS
ok      github.com/hashicorp/terraform-provider-aws/internal/service/bedrockagent       50.933s

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