daemon: Do not remove revNAT if removing svc fails
daemon: Do not remove revNAT if removing svc fails

It has been observed that the daemon can receive the duplicate
events for a k8s svc removal, e.g.:

    msg="Kubernetes service definition changed" action=service-deleted endpoints= k8sNamespace=default k8sSvcName=migrate-svc-6 service="frontend:10.104.17.176/ports=[]/selector=map[app:migrate-svc-server-6]" subsys=daemon
    <..>
    msg="Kubernetes service definition changed" action=service-deleted endpoints= k8sNamespace=default k8sSvcName=migrate-svc-6 service="frontend:10.104.17.176/ports=[]/selector=map[app:migrate-svc-server-6]" subsys=daemon
    g msg="Error deleting service by frontend" error="Service frontend not found 10.104.17.176:8000" k8sNamespace=default k8sSvcName=migrate-svc-6 obj="10.104.17.176:8000" subsys=daemon
    msg="# cilium lb delete-rev-nat 32" k8sNamespace=default k8sSvcName=migrate-svc-6 subsys=daemon
    msg="deleting L3n4Addr by ID" l3n4AddrID=33 subsys=service

In such situations, the daemon tries to remove the revNAT entry twice,
which can lead to a removal of a valid revNAT entry if in between the events
the daemon creates a new service with the same ID.

Fix this by skipping the revNAT removal if the frontend removal fails.

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

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