Graduate APIVersion to elbv2.k8s.aws/v1

[M00nF1sh]

We have been stuck with v1beta version for our CRDs for a long time, i think it's time to graduate it to v1.
Creating this PR to track a few actions items before we can use v1:

1. We should have a workflow that checks all CRDs fields adheres to k8s API convention
   • e.g. check optional fields have both "+optional" and "omitempty"
   • e.g. check optional fields are pointer type except when it's default value is nil (slice/map)
2. In our PR template, ask authors to read https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md before adding new CRD fields
3. Add a conversion Webhook to facilitate API changes
4. Remove the v1alpha1 API
5. TODO API changes for v1:
   1. rename IngressClassParams.spec.listeners.listenerAttributes to be IngressClassParams.spec.listeners.attributes
      • Unlike the 'loadBalancerAttributes', the 'listenerAttributes' are already configured on 'listeners'.
        This approach is straightforward and aligns with the Kubernetes API convention."
      • It matches ELBv2 ModifyListenerAttributes where it's simply 'attributes' in ModifyListenerAttributes
   2. rename IngressClassParams.spec.certificateArn to be IngressClassParams.spec.certificateARNs
      • It reflects that it's a list instead of a single item
      • It aligns with k8s api convention(use the same case for abbreviation ARN), and aligns with targetGroupARN in TGB API.
   3. change IngressClassParams.spec.subnets.tags to use structured fields instead of map[string][string]
   • see https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#lists-of-named-subobjects-preferred-over-maps
   • when doing so, add a new field called matchTags []TagSelectorRequirement

     matchTags:
     - key: my-key
       values: ["tag-value1", "tag-value2"]
     

     • This is similar to "matchExpressions" in metav1.NodeSelector, and we might extend it by add a "operator" to support different tag filters when needed.
   4. remove the "vpcID" & "ipAddressType" from the "TargetGroupBinding.spec" CRD.
      • Those "TargetGroup" specific attributes shall be obtained during TGB reconciliation instead of persisted as part of TGB spec.
      • We cannot keep adding new "TargetGroup" specific attributes into TGB spec in order to use them during reconcile, it's not scalable.
   5. consider to change "TargetGroupBinding.spec.targetType" to be required instead of "optional".
      * We can avoid doing elbv2 api calls as part of webhook.
      * The targetType in theory is not same as targetType of targetGroup. (e.g. ideally we can register node ports targets into targetGroup of ip target type)