`aspire stop --force` not wiping volumes

### Is there an existing issue for this?

- [x] I have searched the existing issues

### Describe the bug

I was told that the `aspire stop --force` command should be equivalent to `docker compose down -v`. It doesn't seem to work though, as you can see on the picture.

All I am looking for is a way to kill the volumes associated with an Aspire stack. Is there another way to do this? Or am I using the command wrong?
If I look in Docker desktop, I just see a lot of different "aspire-managed" volumes, and I have no idea which one is associated with my stack.

I am running Ubuntu 22.

Logs:

[cli_20260821T124753_6ae61f15.log](https://github.com/user-attachments/files/31306347/cli_20260821T124753_6ae61f15.log)
[cli_20260821T121944706_detach-child_28aafd59d70a4d1788611a624b20f283.log](https://github.com/user-attachments/files/31306348/cli_20260821T121944706_detach-child_28aafd59d70a4d1788611a624b20f283.log)

### Expected Behavior

_No response_

### Steps To Reproduce

_No response_

### Exceptions (if any)

_No response_

### Aspire doctor output

_No response_

### Anything else?

_No response_

Start by reproducing `aspire stop --force` on Ubuntu 22 and inspect the attached CLI and detach-child logs. Compare the command's volume cleanup with the stated `docker compose down -v` behavior; done means volumes associated with the Aspire stack are removed without requiring users to identify them manually.

Written by the indexing model from the issue text.