fix(knowledge): re-verify connectorId in updateDocument's atomic write

Greptile P1: updateDocument's content-update/resurrect write only checked
document.id and archivedAt, never connectorId — despite connectorId being
a parameter — so a document a concurrent "delete connector, keep documents"
request already detached could still be matched, resurrected, and
overwritten with connector-sourced content after the connector was deleted.
Adds the same connectorId ownership check already used by the reconciliation
transaction and hardDeleteDocuments in this PR.

Author: waleedlatif1

apps/sim/lib/knowledge/connectors/sync-engine.ts

@@ -1541,7 +1541,17 @@ async function updateDocument(
           // on deletedAt IS NULL, rejects the row and leaves stale content active.
           deletedAt: null,
         })
-        .where(and(eq(document.id, existingDocId), isNull(document.archivedAt)))
+        .where(
+          and(
+            eq(document.id, existingDocId),
+            // A concurrent "delete connector, keep documents" request can null out
+            // connectorId between this sync's liveness check and this write. Without
+            // this check, that now-standalone document would still match on id alone
+            // and get overwritten with connector-sourced content post-detachment.
+            eq(document.connectorId, connectorId),
+            isNull(document.archivedAt)
+          )
+        )
         .returning({ id: document.id })
         .then((rows) => {
           if (rows.length === 0) {