Bump CAPI to v1.5.3

[Ankitasw]

What type of PR is this?
/kind support

What this PR does / why we need it:
This PR bumps CAPI to v1.5.3

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 #

Special notes for your reviewer:

Checklist:

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

Release note:

Bump CAPI to v1.5.3

[Ankitasw]

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

[Ankitasw]

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

[Ankitasw]

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

[AndiDog]

/lgtm

[Ankitasw]

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

[Ankitasw]

/retest

[Ankitasw]

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

[richardcase]

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

[Ankitasw]

PR needs review.

[AndiDog]

/lgtm

[Ankitasw]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Ankitasw

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 [Ankitasw]

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

[Ankitasw]

/cherry-pick release-2.2

[k8s-infra-cherrypick-robot]

@Ankitasw: #4627 failed to apply on top of branch "release-2.2":

Applying: Bump CAPI to v1.5.3
Using index info to reconstruct a base tree...
M	go.mod
M	go.sum
M	test/e2e/data/e2e_conf.yaml
M	test/e2e/data/e2e_eks_conf.yaml
M	versions.mk
Falling back to patching base and 3-way merge...
Auto-merging versions.mk
CONFLICT (content): Merge conflict in versions.mk
Auto-merging test/e2e/data/e2e_eks_conf.yaml
CONFLICT (content): Merge conflict in test/e2e/data/e2e_eks_conf.yaml
Auto-merging test/e2e/data/e2e_conf.yaml
Auto-merging go.sum
CONFLICT (content): Merge conflict in go.sum
Auto-merging go.mod
CONFLICT (content): Merge conflict in go.mod
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Bump CAPI to v1.5.3
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-2.2

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.

[Ankitasw]

/cherry-pick release-2.2

[k8s-infra-cherrypick-robot]

@Ankitasw: #4627 failed to apply on top of branch "release-2.2":

Applying: Bump CAPI to v1.5.3
Using index info to reconstruct a base tree...
M	go.mod
M	go.sum
M	test/e2e/data/e2e_conf.yaml
M	test/e2e/data/e2e_eks_conf.yaml
Falling back to patching base and 3-way merge...
Auto-merging test/e2e/data/e2e_eks_conf.yaml
Auto-merging test/e2e/data/e2e_conf.yaml
Auto-merging go.sum
CONFLICT (content): Merge conflict in go.sum
Auto-merging go.mod
CONFLICT (content): Merge conflict in go.mod
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Bump CAPI to v1.5.3
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-2.2

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.