f-aws_rds_cluster: Support setting CA certificate on create and update

[nikhil-goenka]

Description

Relations

Closes #36258

References

Output from Acceptance Testing

% make testacc TESTS=TestAccRDSCluster_availabilityZones PKG=rds
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go1.22.2 test ./internal/service/rds/... -v -count 1 -parallel 20 -run='TestAccRDSCluster_availabilityZones'  -timeout 360m
=== RUN   TestAccRDSCluster_availabilityZones
=== PAUSE TestAccRDSCluster_availabilityZones
=== RUN   TestAccRDSCluster_availabilityZones_caCertificateIdentifier
=== PAUSE TestAccRDSCluster_availabilityZones_caCertificateIdentifier
=== CONT  TestAccRDSCluster_availabilityZones
=== CONT  TestAccRDSCluster_availabilityZones_caCertificateIdentifier
--- PASS: TestAccRDSCluster_availabilityZones (151.85s)
--- PASS: TestAccRDSCluster_availabilityZones_caCertificateIdentifier (1888.51s)
PASS
ok  	github.com/hashicorp/terraform-provider-aws/internal/service/rds	1955.755s
% make testacc TESTS=TestAccRDSCluster_basic PKG=rds
==> Checking that code complies with gofmt requirements...
TF_ACC=1 go1.22.2 test ./internal/service/rds/... -v -count 1 -parallel 20 -run='TestAccRDSCluster_basic'  -timeout 360m
=== RUN   TestAccRDSCluster_basic
=== PAUSE TestAccRDSCluster_basic
=== CONT  TestAccRDSCluster_basic
--- PASS: TestAccRDSCluster_basic (191.18s)
PASS
ok  	github.com/hashicorp/terraform-provider-aws/internal/service/rds	208.155s

...

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