[OneDiscover][UnifiedDataTable] Apply compact Display options Popover layout

[akowalska622]

Summary

Closes #203377

PR changes visual style of data table options popover, as per this mockup (with couple of adjustments mentioned below):

Note

EDIT
showDisplaySelector customRender in EUI allows us to customize position of controls. I've changed UnifiedDataTableAdditionalDisplaySettings to accept density control as a prop and encapsulated logic for order of controls within this component.

Changes within this PR:

Change range slider style

1. Change range slider style
2. Make the picker more compact, following EUI pattern (no horizontal lines, smaller padding)
3. Move Sample size up

Things we decided not to solve within this PR:
1. Move Sample size up
2. Rename Density to Cell density
4. Add show row stripes toggle

Old view:

New view:

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

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
• ...

[akowalska622]

/ci

[akowalska622]

/ci

[elasticmachine]

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

[akowalska622]

@elasticmachine merge upstream

[davismcphee]

Code changes look good and it works as expected, thanks! I left a couple of minor nits, but nothing blocking.

[elasticmachine]

💚 Build Succeeded

• Buildkite Build
• Commit: 59f4356

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
cloudSecurityPosture	538.0KB	538.3KB	+249.0B
discover	847.6KB	847.9KB	+249.0B
esqlDataGrid	191.1KB	191.4KB	+249.0B
securitySolution	24.9MB	24.9MB	+1.5KB
slo	878.4KB	878.6KB	+249.0B
total			+2.4KB

History

• 💛 Build #274896 was flaky ca5d796
• 💔 Build #274844 failed 4439141
• 💔 Build #274708 failed 402c331
• 💔 Build #274687 failed a6dc4e8
• 💚 Build #274284 succeeded 6c811be
• 💔 Build #274280 failed 7fe60f0

cc @akowalska622