Query results table

[alexjpwalker]

• [ ] When a Match query is executed, the results should be streamed to a table of answers, adding a new row to the table as each new answer comes in.
• [ ] We need to find a smart way of limiting the number of answers rendered at any given time - 50 million elements is not going to be good for performance! I believe Compose's LazyColumn is designed for this exact purpose.

[alexjpwalker]

Okay so basically we need to design the UX of the table properly in order to proceed further with this task.

• Currently, I've disabled text selection, because it causes a bug when hovering over the resizer. However we may want text to be selectable, and also, that bug is most likely fixable by not showing the resizer if the user is selecting text;
• Currently the table breaks when it reaches 999 rows, because Chromium has a hard 1000-row limit on Grid Layout. I've tried using Table Layout instead, but the only way to get the columns to be the widths we want, is to individually style each <td> element, which is a pain in the ass. Block/Flex layout could be made to work, but only if we make the table a set of columns each containing cells (currently it is a set of rows each containing cells), and that would make text selection (potentially) weird, plus it's not really a natural layout for the data, although it is a more natural layout for the, uh, layout.