Orphaned snapshots remain after deleting volumes in CLVM_NG primary storage

### problem

**Issue: Orphaned snapshots remain after deleting volumes in CLVM_NG primary storage**

I'm seeing an issue with CLVM_NG primary storage where snapshots persist for volumes that have already been deleted.

**Reproduction steps:**
1. Deploy a VM with a single root volume that has an associated volume snapshot.
2. Create a new volume from that snapshot.
3. Detach the root volume from the VM.
4. Attach the newly created volume to the VM.
5. Delete the original volume (the one with the associated snapshot).

**Observed behavior:**
The snapshot remains in the system, still linked to the deleted volume.

**Additional observations:**
- When deleting the volume, I can confirm that the LVM logical volumes (LVs) associated with both the root volume and its snapshot **are** deleted on the KVM hosts. So the underlying storage is cleaned up correctly.
- However, the snapshot entry is **not** removed from the database/GUI
- If I then manually delete the snapshot from the **"Volume Snapshot"** section, the operation reports success and the snapshot is no longer displayed in the GUI. This suggests the deletion works, but only when triggered explicitly against the snapshot record.

**Expected behavior:**
Deleting a volume should also remove (or orphan-clean) any snapshots associated with it, or at minimum the snapshot should no longer reference a non-existent volume.

### versions

ACS: 4.23
Primary storage: CLVM_NG
Hypervisor: Rhel9 KVM

Inizia riproducendo il workflow indicato di volume e snapshot su ACS 4.23 con CLVM_NG e segui il percorso di eliminazione del volume attraverso i record del database e della GUI. Confrontalo con il percorso esplicito di eliminazione di Volume Snapshot; il lavoro è completato quando l’eliminazione del volume originale non lascia più uno snapshot che vi faccia riferimento, mentre la pulizia sottostante di LVM rimane intatta.

Scritto dal modello di indicizzazione a partire dal testo della issue.