[Studio] Some Table Editor schema changes can be partially applied if a later step fails

I was looking through the Table Editor code and noticed a few places where one user action is made up of multiple separate schema mutations. The file I was looking at is: `apps/studio/components/interfaces/TableGridEditor/SidePanelEditor/SidePanelEditor.utils.tsx` In particular: - `createColumn` - `updateColumn` - `updateTable` - `duplicateTable` There are already TODO comments above some of these functions saying they should be refactored to run in a single transaction, so I think this may already be known. I wanted to open an issue for it because it looks like it can lead to partially applied schema changes. For example, `createColumn` first creates the column, and then may separately drop/recreate the primary key and add foreign key constraints. If the column gets created successfully but adding the primary key or foreign key fails, the UI operation fails, but the new column is still left in the table. I noticed a similar pattern in `updateTable`, where it can drop the existing primary key, update the table, delete/add/update columns, add the primary key again, and then update foreign keys. Since those happen as separate awaited calls, a failure in the middle would not roll back the earlier changes. One smaller thing I noticed in `duplicateTable`: identity sequence updates are done with `identityColumns.map(async ...)`, but the result of the map is not awaited. So those updates can continue after the function has already moved on, and errors from them may not be handled properly. I do see that some lower-level pg-meta helpers already wrap their own SQL in `BEGIN` / `COMMIT`, so I don't think the issue is that every individual query is untransactional. The issue is more that the whole Table Editor action is not atomic across all of its steps. Would it make sense to compose the SQL for these full operations first and execute it once inside a transaction, similar to how `createTable` already handles the initial table/column/constraint creation? ## Proposed changes I…