[Lens] always retain source order for multi-metric partition chart layers

[drewdaemon]

Summary

Fix #151006

This PR includes two changes

1. the partition_vis expression renderer now orders partitions by the source order. This overrides the default descending-by-size partition sorting behavior in elastic-charts that was being followed previously
2. the dimension buttons and metric column IDs sent to the expression are now both kept in the order specified by the datasource. This allows users to order slices by reordering the dimensions in the layer panel as they can with other visualization types (XY, table). This also fixed a drag-and-drop bug.

When users upgrade, they will see the partitions in their multi-metric charts reorder if the dimensions were out of order with the datasource. That seems fine to me since they can just drag the dimensions into the configuration they had before if they notice/care.

Screen.Recording.2023-02-23.at.2.05.41.PM.mov

Checklist

• Unit or functional tests were updated or added to match the most common scenarios

[elasticmachine]

Pinging @elastic/kibana-visualizations @elastic/kibana-visualizations-external (Team:Visualizations)

[drewdaemon]

@elasticmachine merge upstream

[kibana-ci]

💚 Build Succeeded

• Buildkite Build
• Commit: f6e0a25

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	52.6KB	52.9KB	+280.0B
lens	1.3MB	1.3MB	+70.0B
total			+350.0B

History

• 💚 Build #110130 succeeded a8fac3e
• 💚 Build #109888 succeeded e950ce5
• 💔 Build #109861 failed 39e2803

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

[stratoula]

Although the bug is fixed, now I cant order correctly if I have a terms agg/ Here is an example with the alphabetical ordering:

[stratoula]

I was wrong, this is how it works in main too. It works differently that agg based, this is why I was confused. Fix LGTM

[nickofthyme]

Code changes LGTM