Fix IllegalArgumentException in Search/Replace when columns have been deleted - #3206

Summary

• ColumnStore stores columns in a sparse array where deleted column slots become null and are recycled via a garbageQueue. This means column indices are not contiguous after any deletion.
• findOnNodes and findOnEdges used table.countColumns() as the loop upper bound and called table.getColumn(columnIndex) with a sequential counter. When a gap existed within 0..countColumns()-1, getColumnByIndex threw IllegalArgumentException: The column doesnt exist.
• A secondary bug: columnsToSearch holds actual column store indices (from column.getIndex()), but the filter check compared them against the sequential loop counter — silently wrong after any deletion.

Fix

• Replaced index-based iteration with table.toArray(), which returns a compact, gap-free snapshot of active columns.
• Use column.getIndex() for the columnsToSearch filter check and for foundColumnIndex stored in SearchResult (used by callers such as canReplace, replace, and SearchReplaceUI to call table.getColumn()).
• The startingColumn state (loop position for resuming iteration) continues to use the position within the toArray() snapshot, which is the correct semantic.

Reproducer

1. Open a graph with columns
2. Delete a column (leaving a gap in the store index space)
3. Open Data Laboratory → Search/Replace and run a search
4. → IllegalArgumentException: The column doesnt exist

Made with Cursor