Default instance with a launchagent created by `start-at-login` isn't available after startup

### Description

Yesterday I've tried the new start at login feature that got in with `0.21.0`. Before i've shut down my computer yesterday I've used:

`$> limactl start-at-login default
INFO[0000] The autostart file "/Users/rkoller/Library/LaunchAgents/io.lima-vm.autostart.default.plist" has been created or updated

When I've started my computer today and I tried to directly start a project in DDEV a framework for local development environments in docker i got:

```
$> ddev config
ERRO[0000] app.FindContainerByType(web) failed
ERRO[0000] app.FindContainerByType(web) failed
Could not connect to a Docker provider. Please start or install a Docker provider.
For install help go to: https://ddev.readthedocs.io/en/stable/users/install/docker-installation/
```

When I checked if the lima instance is running:

```
$> limactl list
NAME STATUS SSH VMTYPE ARCH CPUS MEMORY DISK DIR
default Running 127.0.0.1:60022 vz aarch64 4 8GiB 100GiB ~/.lima/default
```
My default instance was shown as running. I then did a `limactl stop` directly followed by a `limactl start` and now docker was available to ddev. And if go into the macos system settings the lima login item is listed:


When clicking the `ì` icon that opens up a finder window:


I've then retested, shut down my computer another time and started it up again. After that instead of trying to run a ddev command i tested with a plain docker command:

```
$> docker ps
Cannot connect to the Docker daemon at unix:///Users/rkoller/.lima/default/sock/docker.sock. Is the docker daemon running?
```
and again with `limactl list`the instance was shown as running

```
$> limactl list
NAME STATUS SSH VMTYPE ARCH CPUS MEMORY DISK DIR
default Running 127.0.0.1:60022 vz aarch64 4 8GiB 100GiB ~/.lima/default
```

For the context i am on a M1pro running macOS Sonoma 14.4 and limactl version 0.21.0 (using the docker template with vz and virtiofs). if you need more informations please let me know.