ROSA TestROSARoleConfigReconcileExist is flaky

[serngawy]

/kind bug
The unit test for ROSARoleConfig TestROSARoleConfigReconcileExist is flaky .

Logs as below

=== RUN   TestROSARoleConfigReconcileExist
    rosaroleconfig_controller_test.go:610: 
        Expected
            <string>: 
        to equal
            <string>: arn:aws:iam::123456789012:role/test-HCP-ROSA-Installer-Role
--- FAIL: TestROSARoleConfigReconcileExist (0.21s)
=== RUN   TestROSARoleConfigReconcileDelete
  GHTTP Received Request: GET - /api/clusters_mgmt/v1/clusters?page=1&search=aws.sts.operator_iam_roles.role_arn+like+%27%25%2Ftest-%25%27
--- PASS: TestROSARoleConfigReconcileDelete (0.36s)
FAIL
E1114 13:12:37.289207   49023 certwatcher.go:232] "error re-watching file" err="no such file or directory" logger="controller-runtime.certwatcher"
E1114 13:12:37.289309   49023 certwatcher.go:240] "error re-reading certificate" err="open /tmp/envtest-serving-certs-2124169368/tls.crt: no such file or directory" logger="controller-runtime.certwatcher"
E1114 13:12:37.289334   49023 certwatcher.go:232] "error re-watching file" err="no such file or directory" logger="controller-runtime.certwatcher"
E1114 13:12:37.289390   49023 certwatcher.go:240] "error re-reading certificate" err="open /tmp/envtest-serving-certs-2124169368/tls.crt: no such file or directory" logger="controller-runtime.certwatcher"
E1114 13:12:37.289419   49023 certwatcher.go:232] "error re-watching file" err="no such file or directory" logger="controller-runtime.certwatcher"
E1114 13:12:37.289469   49023 certwatcher.go:240] "error re-reading certificate" err="open /tmp/envtest-serving-certs-2124169368/tls.crt: no such file or directory" logger="controller-runtime.certwatcher"
FAIL	sigs.k8s.io/cluster-api-provider-aws/v2/exp/controllers	31.260s

https://prow.k8s.io/view/gs/kubernetes-ci-logs/pr-logs/pull/kubernetes-sigs_cluster-api-provider-aws/5739/pull-cluster-api-provider-aws-test/1989318443119153152#1:build-log.txt%3A4549-4555

What steps did you take and what happened:
[A clear and concise description of what the bug is.]

What did you expect to happen:

Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

Environment:

• Cluster-api-provider-aws version:
• Kubernetes version: (use kubectl version):
• OS (e.g. from /etc/os-release):

[k8s-ci-robot]

This issue is currently awaiting triage.

If CAPA/CAPI contributors determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.