VM cannot get network address and start k8s after OS restart

### Description

Colima VM created on Mac M1 Ventura with enabled --kubernetes and --network-address options lose its network address (192.168.106.2) and cannot start k8s after the MacOS reboot. The VM deletion, then the Mac reboot, and the start of a new VM resolves the issue but only until a next Mac reboot

### Version

Colima Version: 0.5.2
Lima Version: 0.15.0
Qemu Version: I don't know

### Operating System

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

### Output of `colima status`

~$ colima status
INFO[0000] colima is running using QEMU
INFO[0000] arch: aarch64
INFO[0000] runtime: docker
INFO[0000] mountType: sshfs
INFO[0000] address:
INFO[0000] socket: unix:///Users/Rostislav_Dublin/.colima/default/docker.sock
INFO[0000] kubernetes: enabled

### Reproduction Steps

1. Create a VM with --kubernetes and --network-address enabled, deploy some k8s workloads, and feel happy...
2. Stop and start your VM if needed, and reconfigure the CPU and memory settings with no problems.
3. Shutdown and reboot your Mac
4. Make sure you cannot successfully get your Kubernetes back to life anymore:
- each time you call "colima start" it now takes too long...
- and during the VM startup you see (in a second terminal window) a blank value in the "colima list" command output ADDRESS column


- and after several minutes of waiting you see the final output message:

- and if you run "docker ps -a" you see all containers (including k8s) stopped:


5. Delete your Colima VM.
6. Reboot your Mac (reboot is mandatory!)
7. Start a new Colima VM
8. Now you have your k8s again... until a next Mac restart

### Expected behaviour

Your VM successfully overcomes OS restarts.

### Additional context

_No response_