[Lens] Improve Datatable content height with custom row height

[dej611]

Summary

Fixes #123654

This PR introduces a new Custom option for the Lens datatable row height, aligning the configuration UI to the Discover/EUI one.
By default the option is set to single:

It is possible to change the option to Auto, which maps to previous Fit row to content.
The new Custom option will default to 2 lines, but it can go up to 20, with a minimum value of 1:

In order to better handle the new state the previous fitRowToContent state prop has been migrated to a combination of these new props:

rowHeight: "single" | "auto" | "custom"
rowHeightLines: number

Note that rowHeightLines is ignored when the rowHeight prop is set to Auto even when forwarded to the table visualization code.

Note: there's a known bug with the Custom option when shrinking down the height. It seems to be a EUI bug (issue TBD)

Note 2: since introducing the custom row height this error appeared from Jest execution:

console.error
      Warning: `NaN` is an invalid value for the `height` css style property.
          in div (created by EuiDataGridCell)
          in EuiDataGridCell (created by Cell)
          in Cell (created by Grid)
          in div (created by EuiDataGridInnerElement)
          in EuiDataGridInnerElement (created by Grid)
          in div (created by Grid)
          in Grid (created by EuiDataGridBody)
          in EuiDataGridBody (created by EuiDataGrid)
          in div (created by EuiDataGrid)
          in div (created by EuiDataGrid)
          in div (created by EuiFocusTrap)
          in EuiFocusTrap (created by EuiDataGrid)
          in EuiDataGrid (created by DatatableComponent)
          in div (created by VisualizationContainer)
          in VisualizationContainer (created by DatatableComponent)
          in DatatableComponent (created by WrapperComponent)
          in WrapperComponent

      at warningWithoutStack (node_modules/react-dom/cjs/react-dom.development.js:530:32)
      at warning (node_modules/react-dom/cjs/react-dom.development.js:1018:27)
      at warnStyleValueIsNaN (node_modules/react-dom/cjs/react-dom.development.js:6443:5)
      at warnValidStyle (node_modules/react-dom/cjs/react-dom.development.js:6466:9)
      at setValueForStyles (node_modules/react-dom/cjs/react-dom.development.js:6530:9)
      at updateDOMProperties (node_modules/react-dom/cjs/react-dom.development.js:7758:7)
      at updateProperties (node_modules/react-dom/cjs/react-dom.development.js:8182:3)
      at commitUpdate (node_modules/react-dom/cjs/react-dom.development.js:9538:3)

I've tried to fix as in EUI exposing the _isJest flag on Jest setup, but that didn't work.

Checklist

Delete any items that are not applicable to this PR.

• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios
• Any UI touched in this PR is usable by keyboard only (learn more about keyboard accessibility)
• Any UI touched in this PR does not create any new axe failures (run axe in browser: FF, Chrome)
• If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
• This renders correctly on smaller devices using a responsive layout. (You can test this in your browser)
• This was checked for cross-browser compatibility

Risk Matrix

Delete this section if it is not applicable to this PR.

Before closing this PR, invite QA, stakeholders, and other developers to identify risks that should be tested prior to the change/feature release.

When forming the risk matrix, consider some of the following examples and how they may potentially impact the change:

Risk	Probability	Severity	Mitigation/Notes
Multiple Spaces—unexpected behavior in non-default Kibana Space.	Low	High	Integration tests will verify that all features are still supported in non-default Kibana Space and when user switches between spaces.
Multiple nodes—Elasticsearch polling might have race conditions when multiple Kibana nodes are polling for the same tasks.	High	Low	Tasks are idempotent, so executing them multiple times will not result in logical error, but will degrade performance. To test for this case we add plenty of unit tests around this logic and document manual testing procedure.
Code should gracefully handle cases when feature X or plugin Y are disabled.	Medium	High	Unit tests will verify that any feature flag or plugin combination still results in our service operational.
See more potential risk examples

For maintainers

• This was checked for breaking API changes and was labeled appropriately

[elasticmachine]

Pinging @elastic/kibana-vis-editors @elastic/kibana-vis-editors-external (Team:VisEditors)

[nreese]

kibina gis changes LGTM
code review

[dej611]

@elasticmachine merge upstream

[flash1293]

You can use multi-row, but the content isn't wrapping (defeating the point of the feature):

[dej611]

@flash1293 fixed the issue.
I removed the class condition by mistake when committing, but now it has been restored:

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: 7f59533
• Storybooks Preview
• Webpack Bundle Analyzer

Metrics [docs]

Public APIs missing comments

Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.

id	before	after	diff
lens	335	341	+6

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
lens	1.1MB	1.1MB	+1.3KB

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id	before	after	diff
lens	44.4KB	44.4KB	+42.0B

Unknown metric groups

API count

id	before	after	diff
lens	386	392	+6

History

• 💛 Build #28687 was flaky 1f5bc0d
• 💚 Build #28473 succeeded 4fa2712
• 💚 Build #28374 succeeded 1a48ad1
• 💔 Build #28355 failed f8927c2
• 💔 Build #28331 failed 0e0757b

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[flash1293]

Tested and works as expected, LGTM