Autoselect prop key

[zoldar]

Changes

Adjustments to the prop_key selection in the Properties breakdown tab.

• If any prop keys are available for the current query, and nothing is yet stored, set the default to the first prop key found
• If nothing is available, set the placeholder value to "No custom properties found", and disable the combobox
• Validate stored properties against what prop keys are actually available for selection. If the stored key is not available, pick the first available as the default.
• Never let an applied custom property filter decide what prop key is selected by default (we now support breakdown by other properties that are not filtered by as well, so this behaviour is irrelevant, even disturbing)

Tests

• Automated tests have been added

Changelog

• Entry has been added to changelog

Documentation

• This change does not need a documentation update

Dark mode

• The UI has been tested both in dark and light mode

[RobertJoonas]

Just pushed another fix in b559d98

Before

The combobox shows up empty when no prop keys are found, yet the user is still able to interact with it and make another request, which is pointless at that point.

Screen.Recording.2024-06-20.at.17.35.50.mov

After

After having returned no results on the initial render of the combobox, we're disabling clicks on it and setting it's placeholder value to "No custom properties found"

Screen.Recording.2024-06-20.at.17.48.41.mov

[RobertJoonas]

Another fix in 574eda1

Before

The previous prop key keeps hanging when the query changes

Screen.Recording.2024-06-20.at.17.58.47.mov

After

Set the propKey to null, and propKeyLoading to true, whenever query changes.

Screen.Recording.2024-06-20.at.18.03.44.mov