feat(insights): string breakdowns

[mariusandra]

Problem

Breakdowns with "other", when the value is returned in a funny format, such as a list ['array of text'], cause type errors when passing through the transform(value, [['txt']], [['txt']], 'other') function that adds the "other"

The only reason I initially added BREAKDOWN_NULL_NUMERIC_LABEL vs BREAKDOWN_NULL_STRING_LABEL was because not everything was returned as a string, and I wanted to preserve sorting when things were returned as numbers, and manually sorted. However other than strings, ints and floats, there are many other types of breakdown values that can be returned... arrays, tuples, bools, datetimes, etc.

Changes

• Change all breakdown values to be returned as strings. The only exception is histogram breakdowns.
• Add "natural sorting" to the insight details table. This way we can still sort breakdowns returned as numbers or arrays in an order that makes sense.
• Seems like breakdown values weren't unbounded to 25 when using HogQL breakdowns. Now they are.
• Fixes a whole bunch of tickets from the HogQL trends errors table
• Changes only flagged code.

Does this work well for both Cloud and self-hosted?

yes

How did you test this code?

• Plenty of tests got updated in the process
• Clicked into the actors modal and everything still worked

[github-actions]

Size Change: 0 B

Total Size: 824 kB

ℹ️ View Unchanged

Filename	Size
frontend/dist/toolbar.js	824 kB

_{compressed-size-action}

[posthog-bot]

📸 UI snapshots have been updated

1 snapshot changes in total. 0 added, 1 modified, 0 deleted:

• chromium: 0 added, 1 modified, 0 deleted (diff for shard 2)
• webkit: 0 added, 0 modified, 0 deleted

Triggered by this commit.

👉 Review this PR's diff of snapshots.

[posthog-bot]

📸 UI snapshots have been updated

1 snapshot changes in total. 0 added, 1 modified, 0 deleted:

• chromium: 0 added, 1 modified, 0 deleted (diff for shard 2)
• webkit: 0 added, 0 modified, 0 deleted

Triggered by this commit.

👉 Review this PR's diff of snapshots.

[robbie-c]

I don't know this code super well but LGTM after ~10 min review, the described change makes sense

[mariusandra]

Thanks 🙌.

Happy to update/revert if anyone has additional thoughts. I want to see if the changes here make a difference, so going to merge it in.

[sentry-io]

Suspect Issues

This pull request was deployed and Sentry observed the following issues:

• ‼️ CHQueryErrorTimeoutExceeded: Code: 159. /api/projects/{parent_lookup_team_id}/query/ View Issue
• ‼️ CHQueryErrorTimeoutExceeded: Code: 159. /api/projects/{parent_lookup_team_id}/query/ View Issue
• ‼️ CHQueryErrorIllegalColumn: Code: 44. /api/projects/{parent_lookup_team_id}/query/ View Issue
• ‼️ CHQueryErrorNumberOfArgumentsDoesntMatch: Code: 42. /api/projects/{parent_lookup_team_id}/query/ View Issue
• ‼️ CHQueryErrorUnknownIdentifier: Code: 47. /api/projects/{parent_lookup_team_id}/query/ View Issue

_{Did you find this useful? React with a 👍 or 👎}