Default selected cluster is inconsistent

[Dugong42]

Hi, I've noticed that the cluster selected by default is inconsistent when there a multiple configured connections.

In my testing, the default cluster looks like the last one of the list (alphabetically by connections.key) which is not intuitive.
Except that when the key starts with a number, AKHQ selects the one with the greater number.

One would expect the ordering of clusters to be consistent with the cluster selected by default. I believe it would be better to select the first one of the list.

Feature request

Could it be made so that the first one (alphabetically) is selected, matching the order displayed?

To go even further, an attribute could be used to determine which is the default cluster to select on startup.

Example: akhq.ui-options.connections.default-selected: <connection_key>

If not set, it would fall back to the first connection alphabetically.

Steps to reproduce

• create multiple connections
• logout/login