[Lens] Loop color mapping in auto-mode

[markov00]

Summary

This PR brings back the legacy behavior of looping colors when more terms than the available colors are visualized in the chart.

fix #168891

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
• Flaky Test Runner was used on any tests changed
• 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

[markov00]

/ci

[kibana-ci]

💔 Build Failed

• Buildkite Build
• Commit: c4690a3
• Interpreting CI Failures
• Cloud Deployment

Failed CI Steps

• Jest Tests #2
• Jest Tests #2
• Jest Tests #5
• Jest Tests #5

Test Failures

• [job] [logs] Jest Tests #2 / AlertPropertyActions does show the property actions with only delete permissions
• [job] [logs] Jest Tests #2 / AlertPropertyActions remove alerts correctly
• [job] [logs] Jest Tests #2 / AlertPropertyActions renders the correct number of actions
• [job] [logs] Jest Tests #2 / AlertPropertyActions renders the modal info correctly for multiple alert
• [job] [logs] Jest Tests #2 / AlertPropertyActions renders the modal info correctly for one alert
• [job] [logs] Jest Tests #2 / AssigneesFilterPopover calls onSelectionChange when 1 user is selected
• [job] [logs] Jest Tests #5 / Color mapping - color generation returns max number of colors defined in palette, use other color otherwise
• [job] [logs] Jest Tests #5 / Color mapping - color generation returns max number of colors defined in palette, use other color otherwise
• [job] [logs] Jest Tests #5 / color mapping load a default color mapping
• [job] [logs] Jest Tests #5 / color mapping load a default color mapping
• [job] [logs] Jest Tests #2 / FileAttachmentEvent renders clickable name

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	40.8KB	40.9KB	+60.0B
expressionTagcloud	23.2KB	23.2KB	+60.0B
expressionXY	132.3KB	132.3KB	+60.0B
lens	1.4MB	1.4MB	+139.0B
total			+319.0B

History

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

[markov00]

closing as replaced by #175144