Enabling a `shared` or `bridged` network causes `lima kubectl cluster-info` to fail

### Description

`colima` is unable to verify that the Kubernetes has started correctly when a `shared` or `bridged` network is used for the underlying VM.

### Version

Colima Version: 0.4.4
Lima Version: 0.11.2
Qemu Version: 7.0.0

### Operating System

- [X] macOS Intel
- [ ] macOS M1
- [ ] Linux

### Reproduction Steps

This used to work, but started failing at some point.

I have set up networking for `lima` as discussed here:

https://github.com/lima-vm/lima/blob/master/docs/network.md

And then in this file: `.lima/_config/override.yaml` I have this:

```yaml
networks:
- lima: bridged
```

When I try to start `colima` with the network uncommented then I get:

```console
INFO[0000] starting colima
INFO[0000] runtime: containerd+k3s
INFO[0000] preparing network ... context=vm
INFO[0000] starting ... context=vm
INFO[0030] provisioning ... context=containerd
INFO[0030] starting ... context=containerd
INFO[0036] provisioning ... context=kubernetes
INFO[0037] starting ... context=kubernetes
FATA[0062] error starting kubernetes: error running [lima kubectl cluster-info], output: "The connection to the server 127.0.0.1:6443 was refused - did you specify the right host or port?", err: "exit status 1"
```

### Expected behaviour

I would expect the VM to come up with no errors and everything in a useable state.

### Additional context

I am able to reproduce this even after recompiling and installing `vde-2` and `vde_vmnet`.