Start command --activate flag not working

### Description

Hello!

I have mac studio ultra(m2) with latest sonoma. (colima run as service with brew)
I started colima container: `colima start --cpu 8 --memory 8 --network-address --profile arm_cpu8_memory8 --vm-type vz --vz-rosetta --activate`
But when restart my mac, colima create new default container :(


### Version

Colima Version: 0.5.6
Lima Version: 0.18.0
Qemu Version: 8.1.2

### Operating System

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

### Output of `colima status`

colima status:


colima status -p :


### Reproduction Steps

1. set colima as service with brew
2. stop colima container, delete all colima container
3. create and start new container: `colima start --cpu 8 --memory 8 --network-address --profile arm_cpu8_memory8 --vm-type vz --vz-rosetta --activate`
4. restart your osx
5. run colima list or docker context ls (start with new default container :( )

### Expected behaviour

I would like to set up my own default container that starts by itself and I don't have to always change and override the new default container

### Additional context

_No response_