fix(uploads): fall through to INSERT if restore-deleted row races a hard delete

If a hard delete races between the initial SELECT and the restore UPDATE,
.returning() yields no row. Previously the function would return undefined
and silently violate the Promise<FileMetadataRecord> contract. Now the
function falls through to the INSERT path, which already handles
uniqueness races via the 23505 catch.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>

Author: waleedlatif1

apps/sim/lib/uploads/server/metadata.ts

@@ -56,7 +56,9 @@ export async function insertFileMetadata(
       .where(eq(workspaceFiles.id, existingDeleted[0].id))
       .returning()
 
-    return restored
+    if (restored) {
+      return restored
+    }
   }
 
   const existing = await db