Reconcile the ovn-controller pod in a replaced node

Issue

In an OpenStack RHOSO 18 deployment, the ovn-controller pod must be deployed in any node with dataplane connectivity. If the node is replaced without following the procedures for scaling down and scaling up, the OVNController type resource keeps the previous node hash. For example:

$ oc get ovncontrollers ovncontroller --output=template --template '{{.status.hash}}'
map[OvnConfigHash-master-0:n85h576h576hffh9dhb8h74h84h569hbdh56bh65fh64fhb8h7h7bh659h7bh698h5hbbh59fh69h56ch588h5bbh67ch684hfh54bh54h54q OvnConfigHash-master-1:n646h647hffh589h55bh574h9fh599h57fhd4hffh654h597h5d6h589h549h557hb6h596h699hbh99h9dhd4h566h9dhc6hcch58bh4h77h5fcq OvnConfigHash-master-2:n5bfh598h94h5d9h684h574h649h55bhddh64hc4h58h67ch675h679h6bh5ffh75h559h54fh595h65bh5ffh68h697h697hb5h5b6h5dhd8h569h65dq input:ndh559h6h5cfhffh55fh5ffh96hcch575h56bh679h68bh6h655h98h5c8hbh657h95h88h58bh54fh664h549h598h547h667h687h669h78hbbq]

The previous output is a OVNController resource that has 3 replicas in 3 different nodes (master-0, master-1 and master-2)

If one of the node replicas is redeployed, the ovn-controller-config pod won't be executed again. This pod is in charge of configuring the local Open vSwitch database and creating the physical network bridges. In that case, the local Open vSwitch won't be configured.