Upgrading Colima VM memory ends up by lost of my images

### Description

Hi

I recently tried to upgrade my colima VM memory from 2 to 4gb.
To do that I used the following command :
`colima start --memory 4`

Unfortunately, I discovered that I lost my images and containers.

Fortunately, I kept my volumes and networks.

Seems not so bad as it cleans disk space a bit but Im on an island with very slow connection so it will take soooo long to pull it again ...

I'm on Macbook Air M2.

### Version

colima version 0.8.4
git commit: e2ddc15483af66e9b8a525d779a0cc926f15dbcb

runtime: docker
arch: aarch64
client: v28.3.3
server: v27.4.0
limactl version 1.2.1
qemu-img version 10.1.0
Copyright (c) 2003-2025 Fabrice Bellard and the QEMU Project developers

### Operating System

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

### Output of `colima status`

INFO[0000] colima is running using macOS Virtualization.Framework
INFO[0000] arch: aarch64
INFO[0000] runtime: docker
INFO[0000] mountType: sshfs
INFO[0000] docker socket: unix:///Users/simon/.colima/default/docker.sock
INFO[0000] containerd socket: unix:///Users/simon/.colima/default/containerd.sock

### Reproduction Steps

1. Start colima with `colima start`
2. Pull some images
3. Stop and start colimage with `colima start --memory 4`

### Expected behaviour

I should have a warning or have my images when the VM is recreated.

### Additional context

_No response_