[GUI] Failed `stop` causes GUI to get stuck

**Describe the bug**
After failing to stop an instance the GUI gets stuck on "Waiting for daemon..." while the CLI continues to work.

**To Reproduce**
How, and what happened?
1. run Multipass GUI
2. Go to shell
1. `sudo fsfreeze --freeze /`
2. `sudo ip link set ens3 down`
3. Select instance and press "Stop"
4. Wait for stop to finish
5. Observe "Waiting for daemon..."
6. Observe CLI still works

**Expected behavior**
The GUI continues to be operable after failed stop

**Additional info**
- OS: Ubuntu 24.04
- `multipass version` multipass 1.15.0-dev.306+gfa2b29055
- `multipass info` "info failed: ssh connection failed: 'Socket error: Connection reset by peer'"
- `multipass get local.driver` qemu

**Additional context**
This problem is likely caused by `info` returning an error because of the bad instance.
The GUI can be recovered by running `multipass delete -p `

Reproduce the failure in the GUI using the listed fsfreeze and network commands, then compare the GUI behavior with the CLI after Stop fails. Start by tracing how the GUI handles the failing info result and daemon-wait state. Done means the GUI remains operable after a failed stop, while the CLI continues to work.

Written by the indexing model from the issue text.