Description of problem:
In perfscale udn-density test with churn enabled we see that due to the async nature of UDNs the deletion of namespace can still leave behind old node subnet annotation. 
When we recreate the same UDN we start seeing failures

Version-Release number of selected component (if applicable):

How reproducible: Always

Steps to Reproduce:

1. Run udn-density with churn with 10+ cycles times back to back

pdiak@redhat.com explained the process better here https://redhat-internal.slack.com/archives/CU9HKBZKJ/p1752772946238619?thread_ts=1751558248.287259&cid=CU9HKBZKJ