Fix row bulk delete freeze

[HarshMN2345]

What does this PR do?

(Provide a description of what this PR does.)

Test Plan

(Write your test plan here. If you changed any code, please provide us with clear instructions on how you verified your changes work.)

Related PRs and Issues

(If this PR is related to any other PR or resolves any issue or related to any issue link all related PR and issues here.)

Have you read the Contributing Guidelines on issues?

(Write your answer here.)

[greptile-apps]

Greptile Summary

This PR fixes a UI freeze that occurred when bulk-deleting rows in the spreadsheet view. The fix snapshots the target row IDs before clearing reactive state, resets selections and triggers a grid re-render up-front (before any awaited API calls), and moves $spreadsheetLoading = false into the finally block so the loading indicator always dismisses.

• Row IDs are captured into rowIdsToDelete before selectedRows/selectedRowForDelete are cleared, ensuring the correct set of IDs is passed to all delete API calls and the success notification.
• The grid is force-re-rendered (spreadsheetRenderKey.set) immediately after clearing state, which is the core fix preventing the freeze while API calls are in flight.
• A single row selected via bulk checkbox now routes through the deleteRow (single-row) endpoint instead of the batch path, which is a minor but reasonable behavioral change.

Confidence Score: 4/5

Safe to merge; the change correctly prevents the freeze and follows the existing error-handling pattern with no new API surface.

The logic restructuring is clean and the state reset order is correct. The only outstanding item is a now-dead || 1 fallback in the deletedRowsCount line, which is harmless in practice.

No files require special attention beyond the single changed component.

Important Files Changed

Filename	Overview
src/routes/(console)/project-[region]-[project]/databases/database-[database]/table-[table]/spreadsheet.svelte	Fixes UI freeze during bulk delete by snapshotting row IDs, clearing selections, and triggering a grid re-render before awaiting API calls; introduces a now-unreachable `

_{Reviews (1): Last reviewed commit: "lint issue" | Re-trigger Greptile}

[greptile-apps]

The || 1 fallback is now unreachable dead code. rowIdsToDelete is built as [selectedRowForDelete] or [...selectedRows], so when any deletion occurs its length is always ≥ 1. In the original code the fallback was needed because selectedRows.length was checked separately and could be 0 when only selectedRowForDelete was set — but that split no longer exists here.

Suggested change

	const deletedRowsCount = rowIdsToDelete.length || 1;
	const deletedRowsCount = rowIdsToDelete.length;