k8s: fix mismatched ip families in frontend and backend for a service
k8s: fix mismatched ip families in frontend and backend for a service

* This commit fixes the issue with k8s service where a single serivce
  with multiple families will have mismatched ip families for frontends
  and backends for cilium services. So for a frontend IPv4 address the
  backend might have both IPv4 and IPv6 addresses. Fix this by filtering
  endpoints for a datapath service based on the familiy of the address
  of the frontend.

Signed-off-by: Deepesh Pathak <f919440c3f96a4d11125a0337b02a5a6cc587b4e@gmail.com>

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