[Lens] Refactor field select component as shared

[dej611]

Summary

This PR refactors the field select component into a shared component that can be used outside of the indexpattern datasource area. This is required for #129299 .

The component is an extra layer on top of EUI combobox with specific ES field knowledge + some extra truncation logic for longer names.

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)

[MichaelMarcialis]

Left one comment for your review. Thanks!

[MichaelMarcialis]

Are these classes being applied in the appropriate circumstances? When running locally, I noticed that some items in the field selector weren't being given these classes and accompanying color styling that they would have been given previously.

For example, in the screenshot below, I'd expect @timestamp and agent.keyword fields to be given the incompatible treatment (as the "Median" function was selected).

[flash1293]

Agree with Michael that it seems like there is some information missing in the field list - non-cpmpatible fields are not shown subdued

[dej611]

The issue should be solved now: the typecast was covering the fact that fields were grouped, leading to the error.

[flash1293]

Tested and works as expected, LGTM

[dej611]

@elasticmachine merge upstream

[dej611]

@elasticmachine merge upstream

[kibana-ci]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: e856d88
• Storybooks Preview
• Webpack Bundle Analyzer

Failed CI Steps

• FTR Configs #36

Test Failures

• [job] [logs] FTR Configs #36 / APM API tests basic apm_mappings_only_8.0.0 Top backend spans when data is loaded without a kuery or environment returns the correct spans for the requested spanName

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
lens	923	930	+7

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.2MB	1.2MB	+2.1KB

History

• 💚 Build #55699 succeeded 9f028e0
• 💔 Build #55677 failed bb72cc7
• 💔 Build #55611 failed e125297
• 💚 Build #55510 succeeded 5016bdc
• 💛 Build #53876 was flaky 4b26b63
• 💚 Build #53396 succeeded 2cfa155

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

[MichaelMarcialis]

LGTM!

[alie223323]

Summary

This PR refactors the field select component into a shared component that can be used outside of the indexpattern datasource area. This is required for #129299 .

The component is an extra layer on top of EUI combobox with specific ES field knowledge + some extra truncation logic for longer names.

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