ga.sock Issue - Guest agent does not seem to be running; port forwards will not work

### Description

## I guess my 2 issues are connected:
### Issue one: Inital start up is not working due to ga.sock issues
```
> [hostagent] Forwarding "/run/lima-guestagent.sock" (guest) to "/Users/x/.colima/_lima/colima/ga.sock" (host)
> [hostagent] connection to the guest agent was closed unexpectedlydial unix /Users/x/.colima/_lima/colima/ga.sock: connect: no such file or directory
> [hostagent] The final requirement 1 of 1 is satisfied
> [guest agent does not seem to be running; port forwards will not work]
> DEGRADED. The VM seems running, but file sharing and port forwarding may not work. (hint: see "/Users/x/.colima/_lima/colima/ha.stderr.log")
> degraded, status={Running:true Degraded:true Exiting:false Errors:[guest agent does not seem to be running; port forwards will not work] SSHLocalPort:65010}
```

### Issue two: Network is not working after starting it correctly aftwards
After this i stop the faulty vm by executing `colima stop -f` and restarting is again via `colima start --arch x86_64 --memory 4`
This works fine but after starting a default postgre container im not able to connect to it via curl or psql. Somehow my docker network is broken after that and im not able to make it work.

### Version

colima version 0.6.8
git commit: 9b0809d0ed9ad3ff1e57c405f27324e6298ca04f
limactl version 0.20.1
qemu-img version 8.2.1

### Operating System

- [ ] macOS Intel <= 13 (Ventura)
- [ ] macOS Intel >= 14 (Sonoma)
- [ ] Apple Silicon <= 13 (Ventura)
- [X] Apple Silicon >= 14 (Sonoma)
- [ ] Linux

### Output of `colima status`

### After ga.sock issue
Error
### After restart without working network
INFO[0000] colima is running using macOS Virtualization.Framework
INFO[0000] arch: x86_64
INFO[0000] runtime: docker
INFO[0000] mountType: virtiofs
INFO[0000] socket: unix:///Users/jbremauer/.colima/default/docker.sock

### Reproduction Steps

1. brew remove colima
2. brew autoremove
3. rm -rf ~/.colima
4. brew install colima
5. colima start --arch x86_64 --memory 4

### Expected behaviour

Starts as expected and postgre example container is able to start and i can connect to it

### Additional context

_No response_