Palette by terms

[stratoula]

Summary

Investigation for #119137 and #101942

This PR tries to address two features:

• Give the users the ability to create custom palettes by applying a specific color to a specific term
• Save their custom palettes (either terms or stops palettes) and reuse them

Color terms palettes

The UI follows the Color stops UI. The user has a list of the terms being displayed to the chart and can give whatever color they want. The changes are immediately being displayed in the chart.

• if there are some terms in common, it will color the same terms with the predefined colors and will give random colors of the same palette to the rest
• If there is no term in common, it will color the terms with random colors of the user-created palette
  

Save palettes

There are cases that the user would like to save a palette to reuse it either on the same visualization or in another. For example. creating a color stops ui might take some time and if the user wants to apply the same configuration to other visualizations, this means that she has to re-apply everything.
This PR creates a new SO type, the palette. In my PoC, I have two types of palettes, the terms and the stops palettes. The stops palettes are created/used by table and heatmap while the terms palettes by xy and partition charts.

After being said a palette can be used to another chart.

Checklist

• 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

[stratoula]

@elasticmachine merge upstream

[stratoula]

@elasticmachine merge upstream

[stratoula]

@elasticmachine merge upstream

[stratoula]

@elasticmachine merge upstream

[stratoula]

@elasticmachine merge upstream

[kibana-ci]

💔 Build Failed

• Buildkite Build
• Commit: dc62dfa
• Interpreting CI Failures
• Storybooks Preview

Failed CI Steps

• Default CI Group #4
• Default CI Group #4
• OSS Misc Functional Tests
• OSS Misc Functional Tests

Test Failures

• [job] [logs] Default CI Group #4 / lens app lens color palette tests should allow to pick color palette in xy chart
• [job] [logs] Default CI Group #4 / lens app lens color palette tests should allow to pick color palette in xy chart
• [job] [logs] OSS Misc Functional Tests / runPipeline basic visualize loader pipeline expression tests reusing partial results does some screenshot comparisons
• [job] [logs] OSS Misc Functional Tests / runPipeline basic visualize loader pipeline expression tests reusing partial results does some screenshot comparisons

Metrics [docs]

Module Count

Fewer modules leads to a faster build time

id	before	after	diff
lens	708	713	+5

Public APIs missing comments

Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.

id	before	after	diff
charts	282	288	+6
lens	245	252	+7
total			+13

Async chunks

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

id	before	after	diff
charts	41.8KB	42.0KB	+207.0B
lens	1018.4KB	1.0MB	+16.9KB
total			+17.1KB

Page load bundle

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

id	before	after	diff
charts	58.0KB	58.4KB	+357.0B
lens	40.9KB	41.0KB	+61.0B
total			+418.0B

Saved Objects .kibana field count

Every field in each saved object type adds overhead to Elasticsearch. Kibana needs to keep the total field count below Elasticsearch's default limit of 1000 fields. Only specify field mappings for the fields you wish to search on or query. See https://www.elastic.co/guide/en/kibana/master/development-plugin-saved-objects.html#_mappings

id	before	after	diff
palette	-	4	+4

Unknown metric groups

API count

id	before	after	diff
charts	314	320	+6
lens	262	269	+7
total			+13

History

• 💔 Build #13330 failed dd049f3
• 💔 Build #12734 failed 77602f3
• 💔 Build #11870 failed f1653e1
• 💔 Build #11184 failed 2ab506c

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