[stub] implement a virtual list component for the column profiles

[hamilton]

Rill Developer does not scale well in the column-space; even if you have so many rows, the application's performance drags down when viewing & editing a model with many columns. There are a number of solutions to this problem, but usually virtualization is the solution most UI engineers implement.

We're already using Tanstack Virtual for our tables. It makes sense to implement virtualization for the column profiles as well, which will likely speed up the overall navigation and editing interactions.

A few other experiments:

• use content-visibility: auto to prevent needless drawing for offscreen elements. This doesn't give much of a performance improvement.
• use a plain InteractionObserver for each profile container element, and don't render elements offscreen. While this works fairly well in practice, there is a bit of render jank when the profiles are reordering. It also doesn't correct for overscrolling (in other words, scrolling fast will not render elements fast enough)

[bcolloran]

I believe this issue is now either complete or made obsolete by @djbarnwal 's work on the speeding up the profiles and updating the priority queue? @djbarnwal, could you please confirm that this issue is no longer needed, and if that is the case please close? Thank you!

[djbarnwal]

Hey @bcolloran Virtualization of Column Profile is something we still want to do. As of now if we have say 500 column profiles, the UI would freeze. Virtualization would helps us prioritize the column profiles which are above the fold. Me and @hamilton have discussed this issue and I would be picking this up at some point.

[hamilton]

I'm updating the OP now to reflect where we are today.