When we delete a DualStack Service it has two endpointslices which individually cleanup the Service object

Describe the bug When deleting a Service with both IPFamilies it has two EndpointSlice objects. This causes the second deletion to fail finding the service.

2025/10/05 20:10:56 DEBUG processing endpoint provider=endpointslices ip=10.244.1.8
2025/10/05 20:10:56 DEBUG watcher provider=endpointslices "service name"=kube-vip-service namespace=default endpoints=0 "last endpoint"="" "active leader election"=false
2025/10/05 20:10:56 DEBUG processing endpoint provider=endpointslices ip=fd00:10:244:1::8
2025/10/05 20:10:56 DEBUG watcher provider=endpointslices "service name"=kube-vip-service namespace=default endpoints=0 "last endpoint"="" "active leader election"=false
2025/10/05 20:10:56 ERROR unable to find/stop service uid=f5920295-b83c-4e8b-920d-f7ab1a26a003

To Reproduce Steps to reproduce the behavior:

Run the e2e-service-tests
Observe the logs.

Expected behavior Don't cleanup twice when the service object is deleted or garbage collected instead of the endpointslices.

Screenshots If applicable, add screenshots to help explain your problem.

Environment (please complete the following information):

Kube-vip Version: main