Colima unable to restart on m1 after operating system restart

### Description

We are seeing an issue where colima will not restart after OS X shuts down if colima is running during shutdown.

```shell
➜ ~ colima start --verbose
INFO[0000] using docker runtime
INFO[0000] starting colima
INFO[0000] starting ... context=vm
> msg="Using the existing instance \"colima\""
> msg="errors inspecting instance: [failed to get Info from \"/Users/dipdhanesha/.lima/colima/ha.sock\": Get \"http://lima-hostagent/v1/info\": dial unix /Users/dipdhanesha/.lima/colima/ha.sock: connect: connection refused]"
FATA[0000] error starting vm: error at 'starting': exit status 1
```

### Version

Colima Version:
```shell
➜ ~ colima version
colima version 0.3.4
git commit: 5a4a70481ca8d1e794677f22524e3c1b79a9b4ae
```

Lima Version:
```shell
➜ ~ limactl --version
limactl version 0.10.0
```

Qemu Version:
```shell
➜ ~ qemu-img --version
qemu-img version 6.2.0
Copyright (c) 2003-2021 Fabrice Bellard and the QEMU Project developers
```

### Operating System

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

### Reproduction Steps

1. `colima start`
3. Shutdown Mac OS (without running `colima stop`)
4. Start Mac OS
5. `colima start`

### Expected behaviour

Colima starts successfully

### Additional context

_No response_

The issue is about Colima failing to restart after an OS shutdown on M1 Macs. The error mentions a socket connection failure to the Lima hostagent. Start by examining the Lima integration in Colima's codebase, particularly around instance lifecycle and socket management. Look at the logs and the state files in ~/.lima/colima to understand what's left behind after an improper shutdown. The fix likely involves handling the leftover socket or instance state during a restart.

Rédigé par le modèle d'indexation à partir du texte de l'issue.