fix(backups): pin S3 per volume execution and harden deletes

Store s3_storage_id on scheduled volume backup executions so retention
and recovery use the S3 that received the upload. Extract
DeleteScheduledVolumeBackup for UI and resource deletion, and isolate
database backup retention failures so cleanup errors do not fail the job.

app/Models/S3Storage.php

@@ -69,13 +69,12 @@ class S3Storage extends BaseModel
                 'save_s3' => false,
                 's3_storage_id' => null,
             ]);
-            $volumeBackupIds = ScheduledVolumeBackup::where('s3_storage_id', $storage->id)->pluck('id');
-            ScheduledVolumeBackupExecution::whereIn('scheduled_volume_backup_id', $volumeBackupIds)
+            ScheduledVolumeBackupExecution::where('s3_storage_id', $storage->id)
                 ->update([
                     's3_storage_deleted' => true,
                     's3_cleanup_pending' => false,
                 ]);
-            ScheduledVolumeBackup::whereKey($volumeBackupIds)->update([
+            ScheduledVolumeBackup::where('s3_storage_id', $storage->id)->update([
                 'save_s3' => false,
                 's3_storage_id' => null,
             ]);