Redundant VPC VR goes dual PRIMARY (race condition?)

### problem

When multiple network tiers are brought up in quick succession in a redundant VPC, I can consistently reproduce both VPCs going primary.

This is really bad because the VIP is then owned by both Virtual Routers and it means traffic is getting dropped like crazy, it makes the entire VPC unusable. Restarting the VPC recovers it to a good state.

Please see the comments for debugging information, but in short it appears at least one of the nodes ends up getting munged address information which causes the wrong ips to be programmed on interfaces and the keepalived configs to diverge between nodes which causes the dual primary. The underlying cause of the issue is this munged address information.

### versions

4.21.0

### The steps to reproduce the bug

Use Terraform to create the VPC, network tiers, and VM Instances.
Terraform configuration being used is here: https://github.com/bradh352/terraform-config

### What to do about it?

_No response_

Empieza reproduciendo el estado de doble primario mediante la configuración de Terraform enlazada en el issue, con la VPC, las capas de red y las instancias de VM en CloudStack 4.21.0. Lee la información de depuración de los comentarios y sigue la información de direcciones manipulada a través de la programación de interfaces y de las configuraciones divergentes de keepalived. Se considera terminado cuando la creación rápida de capas de red ya no produce dos VPC primarias ni una VIP compartida, y el comportamiento de recuperación está cubierto por una prueba de regresión adecuada.

Escrito por el modelo de indexación a partir del texto del issue.