Shared networking does not work with vmType vz on Intel Mac?

### Description

I was trying to fix an issue where volume mounts were not showing up on host MacBook. I found references to a fix for this using the mountType of virtiofs. I made sure I had the latest colima installed, then I looked at the `~/.colima/default/colima.yaml` file and found documentation that stated that "virtiofs is limited to macOS and vmType `vz`" and, further that "vz is macOS virtualization framework and requires macOS 13". I am running MacOS 13.4.1 on an Intel MacBook Pro, so I felt it was ok to override the default vmType to be `vz` and the mountType as `virtiofs`, so I put these lines in my `~/.lima/_config/override.yaml` file:
```
vmType: vz
mountType: virtiofs
```

I then deleted the colima context `colima delete`, then started up colima with the modifications to the override.yaml. After doing this, I found that my disk mount for a place outside my MacOS home directory was now working. However, I was unable to log into our local docker registry. More investigation revealed that the registry was up and running, but I could not reach any external server from inside the lima VM.

How do I enable networking?

Additionally, while colima is starting up with the VZ VM type, the colima status information states otherwise:
```
> [hostagent] Shutting down VZ
> [hostagent] Starting VZ (hint: to watch the boot progress, see "/Users/My.Name/.lima/colima/serial.log")

$> colima status
INFO[0000] colima is running using QEMU
INFO[0000] arch: x86_64
INFO[0000] runtime: docker
INFO[0000] mountType: sshfs
```

### Version

Colima Version: 0.5.5
Lima Version: 0.16.0
Qemu Version: ?

### Operating System

- [ ] macOS Intel <= 12 (Monterrey)
- [X] macOS Intel >= 13 (Ventura)
- [ ] macOS M1 <= 12 (Monterrey)
- [ ] macOS M1 >= 13 (Ventura)
- [ ] Linux

### Output of `colima status`
```
$> colima status
INFO[0000] colima is running using QEMU
INFO[0000] arch: x86_64
INFO[0000] runtime: docker
INFO[0000] mountType: sshfs
INFO[0000] socket: unix:///Users/My.Name/.colima/default/docker.sock
```

### Reproduction Steps

1. change override.yaml code to use `vmType: vz` and `mountType: virtiofs`
2. colima delete
3. colima start
4. docker login... (hangs - cannot connect to registry)

### Expected behaviour

networking should still work.

### Additional context

_No response_