[Discover] Fix truncation for longer text in table

[akowalska622]

Summary

Closes #238831

After wrapping cell into a div in purpose of in-table-search (we need a ref there) we lost cell content truncation, because styles applied by EUI are not inherited further.

UI before in-table-search

UI after in-table-search

EUI docs

As a solution, I firstly added a .eui-textTruncate class directly to that new div, however it was then applied to multilines as well and the class forced one-line text render, no matter of body cell lines count.

Eventually I've targeted .euiDataGridRowCell__content--defaultHeight > div (targeting --defaultHeight is already a workaround for one line summary truncation) and applied truncation styles manually. Another possibility would be applying euiTextTruncate() helper, however it doesn't work in an object syntax we use here (following to Emotion standards).

I'm open to refactor to css`` syntax, which accepts euiTextTruncate() if we prefer to use EUI helper, instead of keeping Emotion syntax aligned.

Checklist

Check the PR satisfies following conditions.

Reviewers should verify this PR satisfies this list as well.

• 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
• If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
• This was checked for breaking HTTP API changes, and any breaking changes have been approved by the breaking-change committee. The release_note:breaking label should be applied in these situations.
• Flaky Test Runner was used on any tests changed
• The PR description includes the appropriate Release Notes section, and the correct release_note:* label is applied per the guidelines
• Review the backport guidelines and apply applicable backport:* labels.

Identify risks

Does this PR introduce any risks? For example, consider risks like hard to test bugs, performance regression, potential of data loss.

Describe the risk, its severity, and mitigation for each identified risk. Invite stakeholders and evaluate how to proceed before merging.

• See some risk examples
• ...

[elasticmachine]

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