[Discover] Discover Classic View Filter In/Out placement when truncate:maxHeight is set to 0

[kertal]

Summary

Fixes #128080

When setting truncate:maxHeight to 0 in Advanced settings, CSS for truncating height of Classic table was no longer injected in global CSS.

This led to an issue with the positioning of the filter buttons. It looked like this

This PR takes care of injecting CSS also for the 0 case, so the positioning of the filter buttons works correctly:

What's more, since it takes a refresh of the browser page for the change of the truncate:maxHeight to take effect, there's now a toast displayed when users persisted the change

Steps to test:

1. Enable classic view in Advanced settings by setting doc_table:legacy to On.
2. Go to Discover , add a column with long content to the table, check that filter buttons when hovering look correctly
3. Save the search and create a new Dashboard with it.
4. Goto Advanced setting enable Classic table, set truncate:maxHeight to 0
5. When saving it you should get a toast to reload the page, which you should do.
6. Go to Discover, check that filter buttons on multiline context are positioned correctly.
7. Go to Dashboard, check that filter buttons on the Dashboard using the saved search you've created, look correctly

Checklist

Delete any items that are not applicable to this PR.

• This renders correctly on smaller devices using a responsive layout. (You can test this in your browser)
• This was checked for cross-browser compatibility

[kertal]

this leads to a toast messaging telling the user to reload

[elasticmachine]

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

[kertal]

@elasticmachine merge upstream

[jughosta]

Thanks for fixing it! Tested in different browsers.

[ryankeairns]

Tested on cloud deployment; worked as described.

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: ae473c6
• Storybooks Preview
• Cloud Deployment
• Webpack Bundle Analyzer

Metrics [docs]

Async chunks

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

id	before	after	diff
discover	407.2KB	407.2KB	+84.0B

Page load bundle

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

id	before	after	diff
discover	40.5KB	40.5KB	-30.0B

History

• 💚 Build #37844 succeeded 718f1ae
• 💚 Build #37409 succeeded 11b4070

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

cc @kertal