`brew servcies start colima` does NOT create the `colima` Docker context

### Description

`brew servcies start colima` does NOT create the `colima` Docker context.

### Version

```
$ colima version && limactl --version && qemu-img --version
colima version 0.8.1
git commit: 96598cc5b64e5e9e1e64891642b91edc8ac49d16

runtime: docker
arch: aarch64

limactl version 1.0.3
-bash: qemu-img: command not found
```

### Operating System

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

### Output of `colima status`

```
~ $ colima status -p default
INFO[0000] colima is running using macOS Virtualization.Framework
INFO[0000] arch: aarch64
INFO[0000] runtime: docker
INFO[0000] mountType: sshfs
INFO[0000] socket: unix:///Users/jim/.colima/default/docker.sock
```

### Reproduction Steps

1. Start colima

```
~ $ brew services start colima
```

2. colima status

```
~ $ colima status -p default
INFO[0000] colima is running using macOS Virtualization.Framework
INFO[0000] arch: aarch64
INFO[0000] runtime: docker
INFO[0000] mountType: sshfs
INFO[0000] socket: unix:///Users/jim/.colima/default/docker.sock
```

3. Docker context

```
~ $ docker context ls
NAME DESCRIPTION DOCKER ENDPOINT ERROR
default * Current DOCKER_HOST based configuration unix:///var/run/docker.sock
```

### Expected behaviour

If start colima manually with `colima start -p default`, then it can successfully creates the Docker context.

By the way, how to specify a profile when using `brew services start colima`?

### Additional context

_No response_

Look at the service startup script in the Homebrew formula or the colima source code under cmd/ or internal/. Compare the manual start command 'colima start' with the brew services launch mechanism. Check how Docker context creation is triggered, likely in the initialization steps. Test by modifying the service definition to ensure the context is set.

Vom Indexierungsmodell aus dem Issue-Text verfasst.