[Lens] Partition legend order synced with filters order

[dej611]

Summary

Fix #149034

This PR adds the legend order sync with Lens filters when there's a single category grouping dimension.

While working on the feature I've noticed also that the Nested switch in the Legend popover was always enabled when visible, also when there's a single grouping dimension and the nesting won't apply. So I've created a new disabled state for this specific case with a tooltip explanation of the disabled state.

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-visualizations @elastic/kibana-visualizations-external (Team:Visualizations)

[stratoula]

@dej611 should the order being applied if I have multiple layers with the filters as the parent layer?

[dej611]

In that case it should work only when the legend is not nested (Legend popover => disable Nested switch).
There are some implementation challenges to make it work the custom sorting with nested legend on the EC side, so that scenario is not covered yet.

[stratoula]

This works great! LGTM! I think that we have decided to hide instead of disabling the not applicable settings (talking about the nested switch) but I leave this to @MichaelMarcialis to decide.

[dej611]

I thought about it, but then it feels like adding/showing the control based on the number of bucketed dimensions could make the feature a little bit harder to discover. I think show/hide makes more sense for supported/unsupported features, while in this case the nested is still applied but with no effect by the EC library.
Let's see what @MichaelMarcialis thinks about it.

[MichaelMarcialis]

This works great! LGTM! I think that we have decided to hide instead of disabling the not applicable settings (talking about the nested switch) but I leave this to @MichaelMarcialis to decide.

I thought about it, but then it feels like adding/showing the control based on the number of bucketed dimensions could make the feature a little bit harder to discover. I think show/hide makes more sense for supported/unsupported features, while in this case the nested is still applied but with no effect by the EC library.
Let's see what @MichaelMarcialis thinks about it.

@stratoula, @dej611: If we're saying that nesting will always be "off" when there is a single grouping dimension, my initial instinct is to hide it instead of disabling it. If it were the inverse (i.e. a feature that was always "on" in a certain state), I might be more incline to show it as disabled, but that doesn't sound like the case here.

[MichaelMarcialis]

Code review only. LGTM, after my previous comment about hiding/disabling the nested switch is address.

[kibana-ci]

💛 Build succeeded, but was flaky

• Buildkite Build
• Commit: 02e0cb6

Failed CI Steps

• FTR Configs #4

Test Failures

• [job] [logs] FTR Configs #4 / cases security and spaces enabled: no_public_base_url push_case incident recorder server should format the comments correctly

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
expressionPartitionVis	53.1KB	53.3KB	+260.0B
lens	1.3MB	1.3MB	+208.0B
total			+468.0B

Unknown metric groups

ESLint disabled line counts

id	before	after	diff
securitySolution	432	435	+3

Total ESLint disabled count

id	before	after	diff
securitySolution	512	515	+3

History

• 💚 Build #119690 succeeded 0db4534
• 💚 Build #119448 succeeded ca73c79
• 💛 Build #119401 was flaky fadda81

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