[Lens] Mosaic / mekko vis type

[ghudgins]

Describe the feature:
Expose mosaic from charts in Lens for all the great reasons in the charts PR: elastic/elastic-charts#1113

Describe a specific use case for the feature:
(from the charts PR)

Mosaic plots are often preferred over full, two-layer sunburst such as this. If the secondary partitioning is shared, eg. here, browsers, then sideways comparison is way more feasible than in the case of sunburst or treemap. In this case, the browser order should be shared too.

Mosaic plot is Lens friendly: it works with full-depth partitioning.

[elasticmachine]

Pinging @elastic/kibana-app (Team:KibanaApp)

[flash1293]

This seems like an easy addition because it's similar enough to the existing partition charts we can make it a sub visualization type of the pie visualization (little additional work).

Another option would be to make this a setting for the existing "tree map" visualization type - is it different enough to warrant a new "chart type"?

[ghudgins]

I see them as 2 distinct chart types but @markov00 & @monfera & @MichaelMarcialis should weigh in when they have time

[ghudgins]

discussed briefly in datavis weekly and in the current lens chart type paradigm it makes most sense as its own type until such time we decide to collapse the number of types to just partition (treemap / pie / mosaic)

edit: nevermind the data vis catalog defines it as its own type so we should probably follow that https://datavizcatalogue.com/methods/marimekko_chart.html

[ghudgins]

few extra details after talking with @elastic/datavis:

• Mosaic should always have 2 "Group by"
• because of the 2 group by requirement I don't think mosaic should be higher than treemap which is more flexible (but i'm going to add to our "suggestions meta" the idea that if there are two we should bump mosaic in priority)

[MichaelMarcialis]

In preparation for this feature, I've created a new icon for the mosaic visualization type to be used in the Lens app. Please download here.

[ghudgins]

@alexwizp I confirmed with @markov00 that we do need to put "Experimental" on this as kibana will be the first consumer of this functionality CC @flash1293