[Table] Add renderMode prop

[cmslewis]

Addresses #1374, #1415, #1495

Checklist

• Include tests
• Update documentation (contained in new prop's description)

Changes proposed in this pull request:

• 💎 NEW Table now supports a renderMode?: RenderMode prop:
  • RenderMode.BATCH (default): renders cells in batches to improve performance
  • RenderMode.NONE: renders cells synchronously all at once
• Added a new "Batch rendering" switch to the Table example:
  

Reviewers should focus on:

I designed the prop as a RenderMode enum instead of a useBatchRendering boolean to allow us to support additional rendering modes in the future. See: #1374 (comment), pasted here for your convenience:

Another idea is, instead of a prop useBatchRendering?: boolean;, to add a renderOptimizationMode?: RenderOptimizationMode; prop (working title) that accepts values like:

• RenderOptimizationMode.BATCH: render as many new cells as possible per frame, and no more (this is what we currently have, and this scheme also has the strongest guarantee against bringing the UI to a crawl)
• RenderOptimizationMode.DEBOUNCE: debounce scrolling, hiding cells on scroll start and rendering cells all at once after the scroll event finishes (this has a risk of locking the UI if the cells are small/numerous/complex/have truncated content, e.g.)
• RenderOptimizationMode.NONE: no optimizations, just render everything (useful for smaller tables, but can easily bring the UI to a crawl on larger tables)

(Maybe also a RenderOptimizationMode.THROTTLE for throttling scrolling).

[blueprint-bot]

Fix lint

Preview: documentation | table
Coverage: core | datetime

[gscshoyru]

Can we just call it render mode? And mention that we do optimizations in the docs? That way we can get rid of the extra mouthful.

[cmslewis]

Sure

[blueprint-bot]

Rename to renderMode

Preview: documentation | table
Coverage: core | datetime

[tgreenwatts]