:bug: Workload cluster can't be deleted when itself has service with type LoadBalancer running

/kind bug
The deleting status stuck in Deleting, resources needs to be removed by hand from openstack.

What steps did you take and what happened:
Create a workload cluster, get the kubeconfig, create a service with type LoadBalancer in it.
It uses the same router and network as the kube-apiserver, while the management cluster doesn't know anything of the other LoadBalancer, so it can't delete the router because it is in use.

What did you expect to happen:
Delete workload cluster including all LoadBalancers which belongs to that or at least ignore them and delete the workload cluster properly.

Anything else you would like to add:
It can probably be separated using the OCCM cloud config

Environment:

• Kubernetes version: (use kubectl version)
• OS (e.g. from /etc/os-release):

Start by reproducing the reported flow: create a workload cluster, obtain its kubeconfig, create a LoadBalancer service, and delete the cluster. Review workload-cluster deletion and the OCCM cloud configuration to determine how the shared router and network are handled. Done means the cluster deletion completes without manual OpenStack cleanup, while the LoadBalancer resources are either removed or safely ignored.