VMNet Issues

### Description

`lima` and `colima` rely on `vmnet_socket` for some network setups. Colima installs embedded binaries to `/opt/colima` but it seems to not re-install them if already present.

This seems to be the source of the errors
```
WARN[0016] error setting up network dependencies: error at 'preparing network': error running [/Users/someuser/.nix-profile/bin/colima daemon status default], output: "time=\"2023-01-19T11:44:43-03:00\" level=fatal msg=\"pid file not found: stat /Users/someuser/.colima/default/daemon/daemon.pid: no such file or directory\"", err: "exit status 1" context=vm
INFO[0016] creating and starting ... context=vm
WARN[0016] error setting up reachable IP address: vmnet socket file not found: stat /Users/someuser/.colima/default/daemon/vmnet.sock: no such file or directory
```

present in many issue reports. After running `sudo rm -rf /opt/colima` those two issues seem to be gone.

### Version

Colima Version: 0.5.2
Lima Version: 0.13.0
Qemu Version: 0.7.2

### Operating System

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

### Output of `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/pecigonzalo/.colima/default/docker.sock

### Reproduction Steps

1.
2.
3.

### Expected behaviour

_No response_

### Additional context

_No response_

The issue mentions vmnet socket errors and embedded binaries in /opt/colima. Look at the network setup code in Colima, likely around vmnet_socket handling and the installation logic for binaries. Check how Colima decides to reinstall or skip binaries. The reproduction steps are missing, so start by understanding the code paths for daemon status and socket creation. Verify the fix by testing the removal of /opt/colima and observing the network dependencies.

Written by the indexing model from the issue text.