[UnifiedDocViewer] Migrate table to EuiDataGrid

[kertal]

To align with UnifiedDocViewer the table displaying fields and values should be migrated to make use of EuiDataGrid. While we were implementing float actions in #171365 we figured out, that implementing custom float action would create a custom pattern for handling action on a table. We aim to use consistent patterns for handling tables, and therefore we will move forward by using a different component providing table actions out of the box. This is also used in the main consumer of the UnifiedDocViewer, which is Discover. On top of this, it might also enable us to make use of features like configureable row height ,and cell width, which might be out of scope for the initial implementation ,but could be evaluated during implementation.

Before:

After:

We should relevant actions per column:

• For field: toggle field in column, pin and field exists
• For value: filter for value, filter out value

To be defined for a later phase

Should we include the data grid menus like we do in the main Discover view as well as the count of fields above the table. See:

[elasticmachine]

Pinging @elastic/kibana-data-discovery (Team:DataDiscovery)

[kertal]

@andreadelrio
Some feedback after testing #175787 and discussing in our sync:

• The new design is appreciated also when working with the POC 👍
• Performance impact doesn't seem to be significant, it looks worse in DevTools than in real life, we still need to do some benchmarking
• There were concerns about the control change, generally we think it's better UX, and more aligned to the usage in the DataTable. What we could consider is to show a dedicated control columns when the screen size allows it? So we would keep the old behavior of showing all actions at one sight, while improving the usage of screen size on smaller screens by using EuiDataGrid
• One other thing was asked, if we should consider aligning the scrolling behavior to the usage in Main Discover. So we scroll the body of the Grid and not the whole grid.
• What might be benefical is to allow the user to configure the grid a bit, e.g. by letting users assign a different row height. We recently heard the complain, that with removing the collapse function for large text blobs, this can lead to more scrolling. Users can Pin fields, also search fields, which is helpful, but it's worth to consider, to let then decide about row height