Experimental feature: low quality sort and render

Im experimenting with low quality mode in cases when camera moves quickly to prevent rendering with stale sort order.
Current implementation is available [here](https://adaptive-sort.netlify.app/). Its still very naive and kinda buggy, but shows the idea and tradeoffs. It can be improved with precomputing splats "weight" based on opacity and dimensions and/or non-linear depth/density.
Currently low quality mode is enabled whenever camera moves, but ideally this decision should be made based on latency of sorting and writing depthIndex.
What are you thinking about this feature/idea? Are tradeoffs worth it?
EDIT: there is no progress bar, so you have to wait a little bit in darkness ;)

Start by reviewing the linked experimental demo and the issue's discussion of camera movement, sorting, depthIndex writes, and low-quality rendering. The issue does not identify repository files, tests, or a concrete completion criterion, so the feature's behavior and success conditions need to be clarified before implementation.

Written by the indexing model from the issue text.