feat: add search, column filters and server-driven data mode

[ahmdshrif]

Reopened after the repository was recreated. Combines the previous PR #1 (search and column filters) and PR #2 (server-driven data mode, already merged into this branch).

Search and column filters

• searchText: matches shown cell text, ignoring case and accents. The search index is built on the first search and reused until data or columns change.
• columnFilters: text, values, range and custom filters, by column key.
• Range filters reject NaN, invalid dates and non-numeric cells, and ignore invalid bounds.
• Row keys recompute when keyExtractor changes; identical key arrays keep their identity.
• Example perf monitor reports "long frame intervals" (> 25 ms); README no longer implies virtualization removes whole-dataset work or that Android performance is proven.

Server-driven data mode

• manualSorting: keeps the order of data; the header still shows sort and taps still call onSortChange.
• manualFiltering: shows data without applying searchText or columnFilters locally.
• loading: spinner only while there are no rows; existing rows stay visible during a new query.
• loadingMore, refreshing / onRefresh, onEndReached / onEndReachedThreshold, error / onRetry.
• The app owns fetching, pagination, retries and cancellation.
• Example app: Local and Server tabs. The Server tab pages a fake API (5,000 rows, 50 per page, 700 ms latency) with server-side sort, search and status filter, plus a "Fail next request" switch.

Testing

• 37 unit tests, lint and typecheck pass.
• iOS 26 simulator, Release build: search and filter chips (884 then 53 of 10,000 rows), first page load, load more (50 → 150), failed page shows footer error with Retry while rows stay visible, Retry recovers, server sort, pull-to-refresh.
• Android emulator (API 35), Release build: load more and pull-to-refresh.
• Not tested on a physical device.

Known follow-up

• After a new sort or filter, the list keeps its scroll offset, so a deep scroll position can trigger onEndReached right away. A scrollToTop ref method or reset option would fix this.