Run bcvk libvirt run failed with error `Failed to connect socket to '/run/user/1001/libvirt/libvirt-sock': No such file or directory`

[henrywang]

This's a flaky, I encountered twice. But re-run can make it passed.
Test run: https://github.com/bootc-dev/bootc/actions/runs/20083628634/job/57617488027?pr=1842

$ bcvk libvirt run --name bootc-tmt-2ymlgd0c-tmt-plans-integration-plan-01-readonly --detach --firmware=uefi-insecure --label=bootc.test=1 --bind-storage-ro localhost/bootc-integration
Filtered from 12 to 1 plan(s) based on arguments: ["readonly", "local-upgrade-reboot"]
Found 1 test plan(s): ["/tmt/plans/integration/plan-01-readonly"]

========================================
Running plan: /tmt/plans/integration/plan-01-readonly
VM name: bootc-tmt-2ymlgd0c-tmt-plans-integration-plan-01-readonly
========================================

Error: 
   0: Failed to list existing domains
   1: Failed to list domains: error: failed to connect to the hypervisor
      error: Failed to connect socket to '/run/user/1001/libvirt/libvirt-sock': No such file or directory
      

Location:
   crates/kit/src/domain_list.rs:108

Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.
Failed to launch VM for plan /tmt/plans/integration/plan-01-readonly: Launching VM with bcvk: command exited with non-zero code `bcvk libvirt run --name bootc-tmt-2ymlgd0c-tmt-plans-integration-plan-01-readonly --detach --firmware=uefi-insecure --label=bootc.test=1 --bind-storage-ro localhost/bootc-integration`: 1

[cgwalters]

This is probably a bcvk bug; I think what's happening is that libvirt is auto-creating a socket and we're racing to connect to it?