Add/alb/targetgroupsbindings

[wcarlsen]

Below is the introduction copied from this PR in infrastructure-modules:
In our current setup all nodes are target for the load balancers in place exposing two nodeports each. The targetgroup registration is happening through an autoscalinggroup attachment. This makes all nodes go through a registration and deregistration process and adding on top of this all requests are very, very likely to make an extra network jump from the node to a node that actually has Traefik running.

Things done:

• change service type from nodeport to clusterip for Traefik green variant
• add targetgroupbinding for registering Traefik green pods to the correct targetgroup in AWS. Note that we are adding kustomize label to make sure the is overwritten because spec.targetGroupArn is immutable
• add readiness probe gate label to Traefik green namespace to ensure that status ready for pods is only set if the pod is a healthy registered target for the targetgroup in AWS see https://kubernetes-sigs.github.io/aws-load-balancer-controller/v3.4/deploy/pod_readiness_gate/ for docs