Description
In Kamaji's ingress cleanup procedure, ingress resources that have the same namespace and name as the tenantControlPlane are being mistakenly deleted.
Even if these ingress resources are not managed by Kamaji, they are still removed during the cleanup process.

Steps to Reproduce

1. Deploy a tenantControlPlane with LoadBalancer (LB).
2. Create an ingress resource that is unrelated to Kamaji but has the same namespace and name as the tenantControlPlane.
3. Delete the tenantControlPlane Pod.
4. Observe that Kamaji deletes the ingress resource during its cleanup process, even though it is not a managed resource.

Possible Cause
The ingress cleanup logic in Kamaji identifies resources based on their namespace and name, assuming they are managed if they match a tenantControlPlane, leading to unintended deletions.

Expected Behavior & Request

• Modify Kamaji's ingress cleanup logic to prevent deletion of ingress resources simply based on namespace and name matching tenantControlPlane.
• Improve the verification process to ensure only managed resources are affected by the cleanup.

Related Issues & References
kubernetes/ingress-nginx#12970
haproxytech/kubernetes-ingress#706