`test` command fails to allocate LXD VMs when verbosity is `verbose` or `debug`
Metadata
Current evaluation
No evaluation has been recorded for this issue yet.
Issue body
### Bug Description
When using the `test` command, if verbosity is set to `verbose` or `debug`, LXD VMs will fail to allocate.
### To Reproduce
```
git clone https://github.com/lengau/astral-ty.git
snapcraft test # Works
snapcraft --verbosity=debug test # Fails to allocate the machine.
```
### Relevant log output
```shell
Creating snap package...
Packed astral-ty_0.0.23-8-gbc9e8a8_amd64.snap
Testing platform 'amd64'
Running spread tests
:: 2026-03-17 18:31:55 Project content is packed for delivery (35.93MB).
:: 2026-03-17 18:31:55 If killed, discard servers with: spread -reuse-pid=362911 -discard
:: 2026-03-17 18:31:55 Allocating craft:ubuntu-24.04...
:: 2026-03-17 18:31:58 Cannot allocate craft:ubuntu-24.04: backend "craft" allocate must print ADDRESS=<SSH address> to stdout, got: ""
:: 2026-03-17 18:32:10 Cannot allocate craft:ubuntu-24.04: backend "craft" allocate must print ADDRESS=<SSH address> to stdout, got: ""
:: 2026-03-17 18:32:25 Cannot allocate craft:ubuntu-24.04: backend "craft" allocate must print ADDRESS=<SSH address> to stdout, got: ""
:: 2026-03-17 18:32:40 Cannot allocate craft:ubuntu-24.04: backend "craft" allocate must print ADDRESS=<SSH address> to stdout, got: ""
:: 2026-03-17 18:32:55 Cannot allocate craft:ubuntu-24.04: backend "craft" allocate must print ADDRESS=<SSH address> to stdout, got: ""
:: 2026-03-17 18:33:10 Cannot allocate craft:ubuntu-24.04: backend "craft" allocate must print ADDRESS=<SSH address> to stdout, got: ""
:: 2026-03-17 18:33:25 Cannot allocate craft:ubuntu-24.04: backend "craft" allocate must print ADDRESS=<SSH address> to stdout, got: ""
:: 2026-03-17 18:33:40 Cannot allocate craft:ubuntu-24.04: backend "craft" allocate must print ADDRESS=<SSH address> to stdout, got: ""
:: 2026-03-17 18:33:55 Cannot allocate craft:ubuntu-24.04: backend "craft" allocate must print ADDRESS=<SSH address> to stdout, got: ""
```
Evaluation history
No evaluation history available.