Volumes not destroyed after VM expunging

##### ISSUE TYPE

* Bug Report

##### COMPONENT NAME

~~~
core
~~~

##### CLOUDSTACK VERSION

~~~
4.19.0.1
~~~

##### CONFIGURATION

##### OS / ENVIRONMENT

KVM hosts (both Ubuntu 22 and OL8 as OS) with NFS v4 primary storage
Using library: libvirt 8.0.0
Using API: QEMU 8.0.0
Running hypervisor: QEMU 6.2.0

##### SUMMARY

Some volumes (only ROOT volumes) remains in Destroy state after the related VM is correctly expunged. Trying to manually delete them results in the following error: "cannot unlock file 'path-to-the-qcow2': Permission denied. Libvirtd run as root on the hosts and I found no permission/ownership issues on the qcow2 disks.

##### STEPS TO REPRODUCE

~~~
I'm not really sure on how to reproduce the issue, seems related only to root disks in our environnement, as data disks give no issues if I try to delete them.
~~~

##### EXPECTED RESULTS

~~~
When the VM is expunged also the root disk is deleted as well
~~~

##### ACTUAL RESULTS

~~~
The root disk remain in the UI in "Destroy" state
~~~

The issue names no source file, test, or entry point. Begin by tracing core volume cleanup during VM expunging in the reported KVM/NFS environment and investigate why root volumes remain in Destroy state; done means the root volume is removed with the expunged VM without the reported permission error.

Written by the indexing model from the issue text.