colima ls shows no network address if rosetta used

### Description

I would expect both instances to have a network address regardless of whether I'm using vz / rosetta, but alas, using vz / rosetta for one of them causes it to not get a network address.

### Version

$ colima version && limactl --version && qemu-img --version
colima version HEAD-8aa34d0
git commit: 8aa34d064c629deea88b53bcf2c85924fcb4407f
limactl version 2.0.3
qemu-img version 10.2.0
Copyright (c) 2003-2025 Fabrice Bellard and the QEMU Project developers

### Operating System

- [ ] macOS Intel <= 13 (Ventura)
- [ ] macOS Intel >= 14 (Sonoma)
- [ ] Apple Silicon <= 13 (Ventura)
- [x] Apple Silicon >= 14 (Sonoma)
- [ ] Linux

### Output of `colima status`

```
$ colima status -p arm64
INFO[0000] colima [profile=arm64] is running using QEMU
INFO[0000] arch: aarch64
INFO[0000] runtime: docker
INFO[0000] mountType: sshfs
INFO[0000] address: 192.168.106.3
INFO[0000] docker socket: unix:///Users/dkegel/.colima/arm64/docker.sock
INFO[0000] containerd socket: unix:///Users/dkegel/.colima/arm64/containerd.sock

$ colima status -p avx
INFO[0000] colima [profile=avx] is running using macOS Virtualization.Framework
INFO[0000] arch: x86_64
INFO[0000] runtime: docker
INFO[0000] mountType: virtiofs
INFO[0000] docker socket: unix:///Users/dkegel/.colima/avx/docker.sock
INFO[0000] containerd socket: unix:///Users/dkegel/.colima/avx/containerd.sock
```

### Reproduction Steps

0. colima delete all the things
1. colima start --profile arm64 --arch aarch64 --memory 4 --cpu 2 --network-address
2. colima start --profile avx --arch x86_64 --memory 4 --cpu 2 --network-address --vm-type vz --vz-rosetta
3. colima ls

Here's a log:

```
$ colima start --profile arm64 --arch aarch64 --memory 4 --cpu 2 --network-address
INFO[0000] starting colima [profile=arm64]
INFO[0000] runtime: docker
INFO[0000] preparing network ... context=vm
INFO[0001] creating and starting ... context=vm
INFO[0002] downloading disk image ... context=vm
INFO[0025] provisioning ... context=docker
INFO[0025] starting ... context=docker
INFO[0026] done

# Alas, only one of the two containers gets an address if you use vz / rosetta here
$ colima start --profile avx --arch x86_64 --memory 4 --cpu 2 --network-address --vm-type vz --vz-rosetta
INFO[0000] starting colima [profile=avx]
INFO[0000] runtime: docker
INFO[0000] creating and starting ... context=vm
INFO[0000] downloading disk image ... context=vm
INFO[0068] provisioning ... context=docker
INFO[0075] starting ... context=docker
INFO[0079] done

# The following command should show both machines have an IP address, and does if you didn't choose vz / rosetta
$ colima ls
PROFILE STATUS ARCH CPUS MEMORY DISK RUNTIME ADDRESS
arm64 Running aarch64 2 4GiB 200GiB docker 192.168.106.3
avx Running x86_64 2 4GiB 200GiB docker
```

### Expected behaviour

Both instances should have an IP address.

### Additional context

workaround: remove the options --vm-type vz --vz-rosetta from colima start for the amd instance.