Adding adot addon to AWSManagedControlPlane fails due dependency on cert-manager

/kind bug

What steps did you take and what happened:

I have the adot addon in the AWSManagedControlPlane. The addon requires the cert-manager in order for it to work. (My goal was to install cert-manager using flux after the cluster was created.) If I remove adot addon and install it using aws eks command after the cert manager is installed, then the addon gets removed by the capa provider because it is not part of the AWSManagedControlPlane configuration. If I keep it in the configuration, then I cannot access the cluster using the kubeconfig because the AWSManagedControlPlane fails to update the aws-auth configuration due to the failing addon. The AWSManagedControlPlane has a status of Ready, but describing the resource shows the error and the aws-auth config map is not updated.

What did you expect to happen:

I expect the addon to temporarily fail, but to not cause the aws-auth to not update or other issues with the AWSManagedControlPlane. Once the cert manager is available, the addon should reconcile and be successful.

Environment:

• Cluster-api-provider-aws version: 2.0.2
• Kubernetes version: (use kubectl version): v1.24.12
• OS (e.g. from /etc/os-release): Ubuntu 20.04.6 LTS