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

Bắt đầu bằng cách tái hiện workflow volume và snapshot được liệt kê trên ACS 4.23 với CLVM_NG, đồng thời lần theo đường dẫn xóa volume qua các bản ghi trong cơ sở dữ liệu và GUI. So sánh với đường dẫn xóa Volume Snapshot rõ ràng; được xem là hoàn thành khi việc xóa volume gốc không còn để lại snapshot tham chiếu đến nó, trong khi quá trình dọn dẹp LVM bên dưới vẫn nguyên vẹn.

Do mô hình lập chỉ mục viết ra từ nội dung của issue.