Discover: Limit field table rendering

[flash1293]

Based on #96765

Only renders the first discover:maxDocFieldsDisplayed rows in the field table and a button to show all of them to speed up the UI.

I'm not sure whether this is that helpful. I imagine it can also be confusing because ctrl+F can't be used anymore to find a field in there. Also it's still pretty slow for really large number of fields (multiple thousands) - what do you think @kertal ? A really nice solution would probably be using data grid and virtualized scrolling.

This is meant as a quick fix for 7.13 if we decide to merge it

[skip ci]

[kertal]

I'm not sure whether this is that helpful. I imagine it can also be confusing because ctrl+F can't be used anymore to find a field in there. Also it's still pretty slow for really large number of fields (multiple thousands) - what do you think @kertal ? A really nice solution would probably be using data grid and virtualized scrolling.

Thanks a lot & Good point @flash1293, so it improves performance, but on the other hand as you said it could break workflows for users like ctrl+F (I think we could add data grid and a custom search here, in general overwork)

Generally this solution would be a quick fix, as you said, also not sure if we shouldn't wait and go for a nice solution (we need also take care of multi field rendering), what do you think @timroes @majagrubic

[flash1293]

Discussed this with @kertal and we decided this level of integration isn't providing much value, so closing this. We would prefer a switch to a paginated eui basic table with a field name search input on top. @kertal Is there an issue for this already?

[kertal]

Discussed this with @kertal and we decided this level of integration isn't providing much value, so closing this. We would prefer a switch to a paginated eui basic table with a field name search input on top. @kertal Is there an issue for this already?

@flash1293 starting one to collect several tasks and todos targeting the doc viewer: #97649