Data Source route53_resolver_rules filter by DomainName

[AliAllomani]

Description

Adding new argument domain_regex to data.aws_route53_resolver_rules to support retrieving Route53 resolver rules by domain name

Relations

Closes #35397

References

Output from Acceptance Testing

% make testacc TESTS=TestAccRoute53ResolverRulesDataSource_domainRegex PKG=route53resolver
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./internal/service/route53resolver/... -v -count 1 -parallel 20 -run='TestAccRoute53ResolverRulesDataSource_domainRegex'  -timeout 360m
=== RUN   TestAccRoute53ResolverRulesDataSource_domainRegex
=== PAUSE TestAccRoute53ResolverRulesDataSource_domainRegex
=== CONT  TestAccRoute53ResolverRulesDataSource_domainRegex
--- PASS: TestAccRoute53ResolverRulesDataSource_domainRegex (18.79s)
PASS
ok      github.com/hashicorp/terraform-provider-aws/internal/service/route53resolver    67.960s



% make testacc TESTS=TestAccRoute53ResolverRulesDataSource_nonExistentDomainRegex PKG=route53resolver
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go test ./internal/service/route53resolver/... -v -count 1 -parallel 20 -run='TestAccRoute53ResolverRulesDataSource_nonExistentDomainRegex'  -timeout 360m
=== RUN   TestAccRoute53ResolverRulesDataSource_nonExistentDomainRegex
=== PAUSE TestAccRoute53ResolverRulesDataSource_nonExistentDomainRegex
=== CONT  TestAccRoute53ResolverRulesDataSource_nonExistentDomainRegex
--- PASS: TestAccRoute53ResolverRulesDataSource_nonExistentDomainRegex (13.40s)
PASS
ok      github.com/hashicorp/terraform-provider-aws/internal/service/route53resolver    59.117s
...

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