✨ Virtualized autocomplete

[oddvernes]

resolves #1909

Remains to figure out a musterious error message in storybook and look into if i can make virtualization optional (its a bit decentralized with changes various placed that would need to be toggled)

[oddvernes]

I added a multiline prop which is false by default. This is mainly relevant if someone have autoWidth set and the text overflows. By default text is cut off with ellipsis, but when you add multiline the text will wrap. This also changes virtualizer settings to measure height per item, so it adds a bit of performance overhead. The old behaviour was always wrap, but then we didnt have the performance penalty either.

I am uncertain if i should add a virtualizerOverscan prop or leave it hardcoded at 25. It sets how many elements are rendered above and below visible viewport. Lower numbers introduce glitchy appearance when scrolling fast as items struggle to render fast enough, while with bigger numbers the scrolling is mostly fine but adds more up front delay on opening/searching/dragging scrollbar. I find 25 to be a good compromize but perhaps users would want more control over this?

[oddvernes]

There was an issue where autocomplete items would not resize when switching between comfortable and compact, but I found a workaround for this.

Finally the last outstanding issue, in the storybook Autocomplete stories, at least when running locally you'll probably see this in the console everytime opening the dropdown:

This is some bug in storybook where window.onerror is captured but fails to send as xhr

If I intercept this window.onerror myself, it turns out the error is ResizeObserver loop limit exceeded. It means ResizeObserver was not able to deliver all observations within a single animation frame. It is benign and can be ignored.

[denektenina]

LGTM