fix: prioritize data grid save over sidebar edits in close-with-save flow

saveAndClose() checked rightPanelState.editState.hasEdits before
changeManager.hasChanges, causing it to take the sidebar-only save path
(which doesn't execute SQL) when the inspector panel reflected data grid
edits. This matched the user's report: Cmd+W → Save behaved identically
to Cmd+W → Don't Save.

The regular saveChanges() already had the correct priority order (data
grid first, sidebar second). This aligns saveAndClose() with that logic.

Author: datlechin

TablePro/Views/Main/MainContentCommandActions.swift

@@ -358,22 +358,27 @@ final class MainContentCommandActions {
             return
         }
 
-        // Sidebar edits
+        // Data grid changes take priority (synced to sidebar editState,
+        // and the data grid path uses the correct plugin driver for SQL generation)
+        if coordinator.changeManager.hasChanges {
+            let saved = await withCheckedContinuation { continuation in
+                coordinator.saveCompletionContinuation = continuation
+                saveChanges()
+            }
+            if saved {
+                performClose()
+            }
+            return
+        }
+
+        // Sidebar-only edits (made directly in the inspector panel)
         if rightPanelState.editState.hasEdits {
             rightPanelState.onSave?()
             performClose()
             return
         }
 
-        // Data grid changes: await the async save via continuation
-        let saved = await withCheckedContinuation { continuation in
-            coordinator.saveCompletionContinuation = continuation
-            saveChanges()
-        }
-
-        if saved {
-            performClose()
-        }
+        performClose()
     }
 
     private func saveFileToSourceURL() {