Add ClusterSecurityGroupsReadyCondition to managedcontrolplane's patchObject

[pydctw]

What type of PR is this?
/kind bug

What this PR does / why we need it:
While reviewing #3157 and doing more investigation, I found that ClusterSecurityGroupsReadyCondition is not part of managedcontrolplane's patchObject function's owned conditions.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #2180

Special notes for your reviewer:

Checklist:

• squashed commits
• includes documentation
• adds unit tests
• adds or updates e2e tests

Release note:

NONE

[k8s-ci-robot]

@pydctw: 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/test-infra repository.

[pydctw]

/test pull-cluster-api-provider-aws-e2e-eks

[pydctw]

CAPA log from pull-cluster-api-provider-aws-e2e-eks doesn't have error patching conditions: The condition \"ClusterSecurityGroupsReady\" was modified by a different process anymore. This was also the case when I tested it locally.

I checked the past 5 runs from the periodic-eks-e2e-main and they all had this error consistently.

Was this the root cause of #2180? Will run e2e test a few times to confirm that the error is gone.

[pydctw]

/test pull-cluster-api-provider-aws-e2e-eks

[pydctw]

Collecting CAPA log from eks e2e test runs - no error patching conditions observed

• 1st run
• 2nd run
• 3rd run

[pydctw]

/test pull-cluster-api-provider-aws-e2e-eks

[Ankitasw]

/lgtm

[pydctw]

/assign @richardcase
for approval

[Ankitasw]

@richardcase @sedefsavas I think this is pending for approval.

[richardcase]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: richardcase

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [richardcase]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[pydctw]

/test pull-cluster-api-provider-aws-build