fix(tables): skip pendingDeleteMask for bounded background deletes

The bounded-delete commit (f1ee3e9) persisted maxRows and omitted doomedCount
but the pendingDeleteMask guard that makes it work was left uncommitted, so the
shipped mask still hid every filter+cutoff match — over-hiding the rows beyond
maxRows that the job never deletes (they vanished from reads until the job ended,
then reappeared). Return no mask when maxRows is set: a bounded delete is
eventually consistent (rows disappear as deleted), like a bounded update.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

Author: TheodoreSpeaks

apps/sim/lib/table/rows/service.ts

@@ -855,6 +855,11 @@ export async function pendingDeleteMask(table: TableDefinition): Promise<SQL | u
   if (!job?.payload) return undefined
   const scope = job.payload as TableDeleteJobPayload
 
+  // A bounded delete (explicit limit) deletes only the first `maxRows` matches, so the filter-based
+  // mask — which hides every match — would over-hide the rows beyond the cap this job never touches.
+  // Leave those reads unmasked; the bounded delete is eventually consistent like a bounded update.
+  if (scope.maxRows !== undefined) return undefined
+
   const doomedParts: SQL[] = []
   if (scope.filter && Object.keys(scope.filter).length > 0) {
     try {