k8s: Wait for CNP status controller to exit when handling CNP delete
k8s: Wait for CNP status controller to exit when handling CNP delete

This ensures that no old CNP status controller can continue running before a
new CNP with an identical name can be added again. This fixes a bug where a CNP
controller from a previous CNP with a conflicting name can continue update the
status  incorrectly if a CNP is deleted and re-added.

Signed-off-by: Thomas Graf <5f50a84c1fa3bcff146405017f36aec1a10a9e38@cilium.io>

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