KVM: Live migration of SSVM fails with dedicated VLAN

### problem

Live migration of SSVMs fails on KVM when the zone has a dedicated storage network IP range configured with a VLAN. The destination agent never creates the storage VLAN bridge during
PrepareForMigrationCommand, so libvirt cannot find the bridge from the source VM's XML and aborts

This is because the storage network is created with broadcast_domain_type: Native and broadcastUri: storage://
And In BridgeVifDriver.createStorageVnetBridgeIfNeeded():
```

if (!Networks.BroadcastDomainType.Storage.equals(nic.getBroadcastType()) || nic.getBroadcastUri() == null) {
return storageBrName; // exits early and bridge is never created
}
```

the above check causes it to exit early and never create the bridge on the destination host

### versions

4.20.3 onward

### The steps to reproduce the bug

Steps to Reproduce

1. Create a zone with KVM hosts
2. Add a pod management network IP range (untagged)
3. Add a Storage Network IP Range to the pod with a non-zero VLAN ID (storage_vlan)
4. Start the zone - system VMs are created; confirm br- exists on the source host
5. Attempt live migration of the Secondary Storage VM to the other host
6. Migration fails with Cannot get interface MTU on 'br-': No such device

### What to do about it?

_No response_

Comienza en BridgeVifDriver.createStorageVnetBridgeIfNeeded() y sigue cómo PrepareForMigrationCommand gestiona la red de almacenamiento durante la migración en vivo. Reproduce el problema con una zona KVM que use una VLAN de almacenamiento dedicada y, a continuación, verifica que el destino cree el puente de la VLAN de almacenamiento y que la migración de la Secondary Storage VM se complete correctamente.

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