fix(table): drop run-mutation refetch so SSE patches aren't overwritten

useRunColumn.onSettled was canceling in-flight queries and invalidating the
rows query — leftover behavior from the polling era. With the SSE stream
now keeping the cache live via incremental patches, this refetch races the
stream and snaps the cache back to whatever DB shows at the refetch moment,
which can lag the just-arrived queued/running events. Cells appeared stuck
on the optimistic 'pending' even though the SSE was delivering the real
transitions.

Author: TheodoreSpeaks

apps/sim/hooks/queries/tables.ts

@@ -1236,14 +1236,10 @@ export function useRunColumn({ workspaceId, tableId }: RowMutationContext) {
     onError: (_err, _variables, context) => {
       if (context?.snapshots) restoreCachedWorkflowCells(queryClient, context.snapshots)
     },
-    onSettled: async () => {
-      // Cancel any in-flight poll first — without this, a poll started during
-      // the mutation but lands AFTER it resolves can clobber the optimistic
-      // patch with stale data, producing a queued → cancelled → queued flicker
-      // before the authoritative refetch arrives.
-      await queryClient.cancelQueries({ queryKey: tableKeys.rowsRoot(tableId) })
-      await queryClient.invalidateQueries({ queryKey: tableKeys.rowsRoot(tableId) })
-    },
+    // No onSettled refetch — useTableEventStream keeps the cache live via SSE.
+    // A post-mutation refetch here would race the stream's incremental patches
+    // and snap the cache back to a DB snapshot, losing the just-arrived
+    // status transitions.
   })
 }