SQL Editor doesn't report affected row count for UPDATE/DELETE

- [x] I confirm this is a bug with Supabase, not with my own application. - [x] I confirm I have searched the Docs, GitHub Discussions, and Discord. ## Describe the bug After running an UPDATE in the SQL Editor, the results panel shows "0 rows" and "Success. No rows returned." Both suggest nothing happened, but the statement did update a row. There is no way to confirm how many rows were actually affected. ## To Reproduce 1. Open the SQL Editor on a project with a table containing at least one row 2. Run a statement that updates exactly one row without returning it: ```sql update position_log set notes = notes where id = (select id from position_log limit 1); ``` 3. Look at the results panel Result: "0 rows" and "Success. No rows returned", despite one row being updated. ## Expected behavior Postgres reports an affected-row count for these commands (e.g. UPDATE 1). Surfacing that count — or at least not showing "0 rows" when rows were modified — would let users verify the statement matched what they intended. psql and most SQL clients show this by default. ## Screenshots <img width="1872" height="1098" alt="Image" src="https://github.com/user-attachments/assets/33b83c58-7cf6-477b-b252-e0d93f7d1f77" /> ## System information - OS: macOS 14.8.2 (arm64) - Browser: Chrome 149 - Version of supabase-js: N/A (dashboard, not client library) - Version of Node.js: N/A - Hosted Supabase ## Additional context `UtilityTabResults.tsx` appears to branch only on whether the returned row array is empty. The response from /platform/pg-meta/{ref}/query seems to carry rows only, with no command tag or row count, so this may need a change upstream of the dashboard.