[Lens] Better defaults for top values odering

[flash1293]

Fixes #87115

This PR changes the default rank behavior of the top values function to make it more likely to pick the desired output without explicit user interaction.

It introduces a new piece of state for a dimension, recording whether it's using alphabetical sorting because the user explicitly chose alphabetical or whether there was no other option

Behaviors:

• If a sortable metric gets added and a top values dimension is currently using alphabetical sorting because there was no other option, it will pick up descending sorting by this new metric
• If a top values dimension is using alphabetical sorting because of an explicit user interaction, it won't be affected by changing metric dimensions
• If the metric a top values dimension is ranked by gets removed and there is another metric to rank by, it will switch over to that one
• If the metric a top values dimension is ranked by gets removed and there is no other metric to rank by, it will switch over to ascending alphabetical ordering

[elasticmachine]

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

[wylieconlon]

Nice, this works exactly how I expected it to. My only comment is about whether we want to store this in the persisted state vs local state only: if you open a saved visualization that uses a fallback it will have the same state.

[flash1293]

@elasticmachine merge upstream

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: 3eb588f
• Storybooks Preview
• Documentation Changes

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
lens	943.8KB	944.5KB	+732.0B

History

• 💚 Build #119891 succeeded 4da2025
• 💔 Build #119747 failed a36a06e
• 💔 Build #119623 failed 9c41133
• 💔 Build #119568 failed 1d7cb23

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

[flash1293]

My only comment is about whether we want to store this in the persisted state vs local state only: if you open a saved visualization that uses a fallback it will have the same state.

I see the point - I thought it would make sense to persist the flag as well. Let's see whether people get annoyed with it.

[kibanamachine]

💚 Backport successful

Status	Branch	Result
✅	7.x

This backport PR will be merged automatically after passing CI.