k8s: Provision NodePort per ClusterIP IP protocol
k8s: Provision NodePort per ClusterIP IP protocol

Previously, we tried to provision a NodePort service for IPv6 depending
on whether `--enable-ipv6` was set to true which was wrong, as enabling
IPv6 does not mean that each Service definition will be in IPv6.

Unfortunately, "net.ParseIP([...]).To{4,16}()" is not reliable enough
to determine whether a clusterIP is in IPv6 or IPv4, thus the hack:
https://github.com/asaskevich/govalidator/pull/100.

Fixes: 64568ff41 ("k8s: Add NodePorts field to Service struct")
Signed-off-by: Martynas Pumputis <6b0d31c0d563223024da45691584643ac78c96e8@lambda.lt>

cilium-team/cilium,cilium/cilium,michi-covalent/cilium,tgraf/cilium,cilium/cilium,tklauser/cilium,michi-covalent/cilium,cilium/cilium,tklauser/cilium,tklauser/cilium,tgraf/cilium,cilium-team/cilium,tgraf/cilium,michi-covalent/cilium,cilium/cilium,michi-covalent/cilium,tgraf/cilium,tklauser/cilium,tgraf/cilium,cilium/cilium,tgraf/cilium,tklauser/cilium,michi-covalent/cilium