(cherry picked from commit 2be11269)

The address type has already be set to router, set mac address will bring back performance penalty

(cherry picked from commit 28a93927)

(cherry picked from commit 329228d4)

(cherry picked from commit 3bfd82b7)

A temporary workaround, refactor the annotation usage later

(cherry picked from commit eb63f72e)

(cherry picked from commit a09e84d0)

This reverts commit c106afa6.

When receive delete event, we cannot get the origin object anymore, we can just delete the deployment here.

(cherry picked from commit edaf41e0)

(cherry picked from commit 3f8a2b0e)

(cherry picked from commit ff5d3df3)

(cherry picked from commit 86f63f26)

fix trace command in dual stack underlay networking

```
E0926 09:50:20.371312       1 init.go:347] failed to init node kube-ovn-worker. address 100.64.0.3: AddressConflict
E0926 09:50:20.377591       1 init.go:347] failed to init node kube-ovn-control-plane. address 100.64.0.2: AddressConflict

```

(cherry picked from commit 87f9b863)

(cherry picked from commit a99c4200)

Consider the following scenario:
1. A StatefulSet Pod with random IP address allocation is deleted
and soon kube-ovn-contrller is restarted;
2. kube-ovn-controller initailizes IPAM on startup and no IPAM record
for the deleted StatefuleSet Pod is created;
3. A new StatefulSet Pod with the same name is created and
kube-ovn-controller assigns a new IP address to it.