feat(render): merge keybindings in UI

[har7an]

This PR updates the keybindings view in the "hints" section in lazy home.
Activation keys for plugins are now iterated in sorted order (by keys) and
common prefixes, if present, are shown instead of all the individual
keybindings.

Given a config like this:

return {
    {
        'rcarriga/nvim-notify',
        lazy = true,
        keys = {
            { "<leader>N",  desc = "+notifications" },
            { "<leader>Ny", "<Cmd>Notifications<CR>", desc = "history (plain)" },
            { "<leader>Nd", function() require("notify").dismiss() end, desc = "dismiss" },
            { "<leader>Np", function() require("notify").pending() end, desc = "show pending" },
        },
    },
}

The UI entry in the Not Loaded plugins now looks like this:

   ○ nvim-notify  <leader>N

instead of previously:

   ○ nvim-notify  <leader>Nd  <leader>Np  <leader>N  <leader>Ny

As a side-effect, this ensures that, even if no "common prefix" exists, keys
are always shown in sorted order.

Additional remarks

Compound keybindings

I assume that the current implementation fails when "Ctrl"-based keybindings
are mixed with anything that has "C" as a prefix, for example. I'm not sure
about the exact notation of Ctrl-/Alt-keybindings in nvim because I never use
them, but a quick test with this setup:

        keys = {
            { "<leader>C",  desc = "+notifications" },
            { "<leader>Cy", "<Cmd>Notifications<CR>", desc = "history (plain)" },
            { "<leader>C-d", function() require("notify").dismiss() end, desc = "dismiss" },
            { "<leader>Cp", function() require("notify").pending() end, desc = "show pending" },
        },

shortens the whole group to <leader>C in the UI, where it should probably
show <leader>C <leader>C-d instead. In a similar fashion, I assume that a
scenario like this fails as well:

        keys = {
            -- Plain "C" with plain "-"
            { "<leader>C-",  desc = "+notifications" },
            { "<leader>C-y", "<Cmd>Notifications<CR>", desc = "history (plain)" },
            { "<leader>C-d", function() require("notify").dismiss() end, desc = "dismiss" },
            { "<leader>C-p", function() require("notify").pending() end, desc = "show pending" },
        },

although I'm unsure whether this is a realistic scenario to consider here. Is
there something like an iterator over individual/compound keys in the raw data?
Or do I have to check whether C-? is part of a compound binding myself? If
so, do you know of any other compound bindings I should be aware of?

which-key integration

Users of which-key will probably not benefit from this change. That is
because keybinding groups must be registered in which-key directly (so the
"group"-prefix is picked up correctly), so lazy doesn't know about them. Since
keybindings can only be performed once, we cannot just "copy" the which-key
group assignment into lazy just for the UI.

I've opened a PR for which-key that solves this inconvenience, in case
you're interested.

[github-actions]

This PR is stale because it has been open 60 days with no activity.

[har7an]

Rebased onto latest main.

[folke]

I'm not a fan of this. Thank you anyway though!