SLIRP nw driver stops working quite often

### Description

After having some issues with [`gvproxy`](/abiosoft/colima/issues/466), I was suggested to use SLIRP, however I've been noticing that, during the day, it stops working and all the mounting points crash, although I see that the VM is still accessible (`colima ssh` works).
That's the same behaviour I noticed when using Lima directly, because I believe they use SLIRP by default.
The solution right now is to restart colima every time it happens, but is there anything that can be done to tackle this issue at Colima's domain, or would that be something more about Lima or even QEMU?

### Version

Colima Version: 0.5.4
Lima Version: 0.15.0
Qemu Version: 7.2.0

### Operating System

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

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

### Reproduction Steps

1. colima start # keep working on your containers and wait...that will eventually happen

### Expected behaviour

Mounting points to continue to work properly

### Additional context

**docker ps**
`Cannot connect to the Docker daemon at unix:///Users/user/.colima/default/docker.sock. Is the docker daemon running?`

**colima ssh**
```
ash: cd: line 0: can't cd to /Users/user/mysharedfolder: No such file or directory
FATA[0000] exit status 1
```