test: Exclude NodePort services from pre-flight checks
test: Exclude NodePort services from pre-flight checks

Currenly, we have multiple frontends per NodePort BPF service (0.0.0.0,
127.0.0.1, etc). Each of them is stored in the BPF maps, and also in
the daemon.loadBalancer cache (can be retrieved via "cilium service
list").

The service pre-flight check in the integration tests checks whether
each service frontend from the daemon cache has a corresponding one in
k8s ("k8s get svc"). Obviously, the surrogate frontends for NodePort svc
do not exist in k8s, which makes the tests to fail when running with
"--enable-node-port=true".

Ignore the surrogate NodePort frontends in the check for now.

Signed-off-by: Martynas Pumputis <6b0d31c0d563223024da45691584643ac78c96e8@lambda.lt>

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