colima template has no effect

### Description

Hello,

I'm very new to colima and I'm sure I have tried colima 6 or 8 month ago. So first of all `colima delete` to start a fresh setup.
I found a `colima template` command. Nice. I have edited the default template to my needs on a Mac M1...you know, with "vz", "virtiofs", ...

As I have editited the default template I thought just `colima start` should done the job, but after `colima status` I see colima is still working on QEMU. Sorry, don't understand that. Further I have tried `colima start -e` to see the current configuration. Nearly all values are empty and have nothing to do with my default template values. I also tried `colima start -p default`, but the result keeps the same.

Maybe I have miss-understood the meaning of `colima template`.

Can you please explain the usage of `colima template` to me or do I have found a bug?

Nice greetings

Stefan

### Version

Colima Version: 0.5.4
Lima Version: 0.15.1
Qemu Version: 8.0.0

### Operating System

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

### Output of `colima status`

INFO[0000] colima is running using **QEMU**
INFO[0000] arch: aarch64
INFO[0000] runtime: docker
INFO[0000] mountType: sshfs
INFO[0000] socket: unix:///Users/froemken/.colima/default/docker.sock

### Reproduction Steps

1. colima delete
2. colima template
3. modify values to my needs for a Mac M1: vz, virtioFS, ...
4. colima start

### Expected behaviour

After modifying the default values with `colima template` I expect `colima start` will use the defaults from template while start up.

### Additional context

docker context is set correctly:
```
➜ ~ docker context ls
NAME DESCRIPTION DOCKER ENDPOINT ERROR
colima * colima unix:///Users/froemken/.colima/default/docker.sock
default Current DOCKER_HOST based configuration unix:///var/run/docker.sock
desktop-linux
```

Look at the template command implementation in the CLI code, likely under cmd/colima/template.go. Understand how the template is read and applied during colima start. Check the configuration loading order and see why the template values are not being used. Verify the template file location and format. Running colima with debug flags may show the config being loaded.

Vom Indexierungsmodell aus dem Issue-Text verfasst.