feat(backups/CBT): retry data_destroy when error is VDI_IN USE

sometimes the capi take too long to detach the VDI
in this case, the timeout is fixed at 4s, non modifiable
when the timeout is reached the xapi raise a VDI_IN_USE error

this is an internal process of the xapi

This commit add a retry on XO side to give more room for the xapi
to work through this process, as XO already do it one vdi destroying

fix #7826

@xen-orchestra/backups/_runners/_vmRunners/_AbstractXapi.mjs

@@ -290,7 +290,7 @@ export const AbstractXapi = class AbstractXapiVmBackupRunner extends Abstract {
       for (const vdiRef of vdiRefs) {
         try {
           // data_destroy will fail with a VDI_NO_CBT_METADATA error if CBT is not enabled on this VDI
-          await this._xapi.call('VDI.data_destroy', vdiRef)
+          await this._xapi.VDI_dataDestroy(vdiRef)
           Task.info(`Snapshot data has been deleted`, { vdiRef })
         } catch (error) {
           Task.warning(`Couldn't deleted snapshot data`, { error, vdiRef })

@xen-orchestra/xapi/vdi.mjs

@@ -27,6 +27,9 @@ class Vdi {
       noop
     )
   }
+  async dataDestroy(vdiRef) {
+    return await this.callAsync('VDI.data_destroy', vdiRef)
+  }
 
   async create(
     {
@@ -290,5 +293,12 @@ decorateClass(Vdi, {
       return this._vdiDestroyRetryWhenInUse
     },
   ],
+  // same condition when destroying data of a VDI
+  dataDestroy: [
+    pRetry.wrap,
+    function () {
+      return this._vdiDestroyRetryWhenInUse
+    },
+  ],
   exportContent: defer,
 })