When a namespace/project is recreated right after its deletion,
it's possible that the previous kuryrNet CRD is not yet removed,
and Kuryr will try to create another CRD, resulting in k8s conflict
exception. In the meantime, other events handling resources under
the same namespace in question could be inquiring for an annotation
on the namespace, that was not annotated due to the conflict error,
causing the controller to restart.
This commit fixes the issue by adding an annotation to the KuryrNet
CRD with the respective namespace uid, which allows to check
if the existing CRD corresponds to the namespace.
Depends-On: https://review.opendev.org/#/c/677487/
Change-Id: I85d903902b516bfd109078705860540d731886bc
Closes-Bug: 1833712
(cherry picked from commit 37b8e3e6b3)
46b1407dea