karmada: PropagateDeps does not propagate Service

What happened: When I try to use application Failover (https://karmada.io/docs/userguide/failover/application-failover), using propagateDeps: true, the Service related to the Deployment is not migrated on the new cluster. Without Service, application on Destination node cannot be used correctly.

What you expected to happen: To propagate to the other cluster all resources in specified in the same PropagationPolicy of the Deployment.

How to reproduce it (as minimally and precisely as possible): Follow this guide (https://karmada.io/docs/userguide/failover/application-failover/#example), but put a also a Service for that nginx Deployment. Put the Service resource inside the same propagationPolicy. Cordon and delete the pod and wait for tolerationSeconds. At this moment, Deployment should be moved to another cluster, but the related Service remain on the old cluster.

Anything else we need to know?: I have tried with config map (not mounted in the Deployment, just added to the same PropagationPolicy) and I obtain the same behaviour.

Environment:

• Karmada version: 1.7.1
• kubectl-karmada or karmadactl version (the result of kubectl-karmada version or karmadactl version):
• Others: