feat(bedrock): add data sources for prompt routing

[marcinbelczewski]

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 (access controls, encryption, logging) in this pull request.

Description

This PR adds two new data sources for AWS Bedrock Prompt Router functionality:

1. aws_bedrock_prompt_router - Retrieves detailed information about a specific prompt router by ARN
2. aws_bedrock_prompt_routers - Lists all available prompt routers in an AWS account/region

These data sources enable users to discover and reference existing Bedrock prompt routers for intelligent routing of prompts across multiple foundation models.

Relations

Closes #45125

References

• AWS SDK Go v2 - GetPromptRouter
• AWS SDK Go v2 - ListPromptRouters
• AWS Bedrock API Reference - Prompt Router APIs

Output from Acceptance Testing

% make testacc TESTARGS='-run=TestAccBedrockPromptRouter' PKG=bedrock AWS_PROFILE=octo1 AWS_REGION=eu-central-1

=== RUN   TestAccBedrockPromptRoutersDataSource_basic
=== PAUSE TestAccBedrockPromptRoutersDataSource_basic
=== CONT  TestAccBedrockPromptRoutersDataSource_basic
--- PASS: TestAccBedrockPromptRoutersDataSource_basic (11.01s)
PASS
ok  	github.com/hashicorp/terraform-provider-aws/internal/service/bedrock	19.073s

=== RUN   TestAccBedrockPromptRouterDataSource_basic
=== PAUSE TestAccBedrockPromptRouterDataSource_basic
=== CONT  TestAccBedrockPromptRouterDataSource_basic
--- PASS: TestAccBedrockPromptRouterDataSource_basic (13.22s)
PASS
ok  	github.com/hashicorp/terraform-provider-aws/internal/service/bedrock	20.839s

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