Performance benchmarking for table use cases

😯 Problem to Solve

This feature tracks the performance testing that we want to do before telling clients that the table is ready to use. At this point it's a starting point for discussion and a placeholder to remind us to do something.

💁 Proposed Solution

Possible ideas:

1. do nothing. Rely on previously completed manual testing
2. do another round of manual testing
3. Prioritize #614 and add cases for important table behaviors
4. add performance test infrastructure (e.g. Lighthouse) to an SLE app and track how much of the time spent rendering a page is table rendering vs other factors like network activity

📋 Tasks

Start by resolving which proposed direction to pursue: manual testing, the cases in #614, or performance infrastructure such as Lighthouse in an SLE app. Define the table use cases, measurement approach, and completion criteria before choosing files or tests, since the issue names none.