feat: Allow awsmachinepool to be set to 0 for minsize instead of 1 for v1alpha4 and v1alpha3

[tasdikrahman]

/kind feature

Would like the minsize to be 0 instead of the current 1 for both the above api's as the awsmachinepool can scale down to 0

https://github.com/kubernetes-sigs/cluster-api-provider-aws/blob/release-1.5/exp/api/v1alpha4/awsmachinepool_types.go#L45
https://github.com/kubernetes-sigs/cluster-api-provider-aws/blob/release-1.5/exp/api/v1alpha3/awsmachinepool_types.go#L45

related to this #3242

Describe the solution you'd like
[A clear and concise description of what you want to happen.]

Update the min size to 0 for the above API's

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

Environment:

• Cluster-api-provider-aws version: v1.5.5
• Kubernetes version: (use kubectl version): 1.22
• 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/test-infra repository.

[tasdikrahman]

closing this as discussed in slack here, both the above API's have been deprecated, closing this