fix(octo-nvim): which-key description and color for nested entries

[RayJameson]

Yet another one of like #376 and what after it. Also, remove default mappings which the plugin sets, to avoid keymap mess

[github-actions]

Review Checklist

Does this PR follow the [Contribution Guidelines](development guidelines)? Following is a partial checklist:

Proper conventional commit scoping:

• If you are adding a new plugin, the scope would be the name of the category it is being added into. ex. feat(utility): added noice.nvim plugin

• If you are modifying a pre-existing plugin or pack, the scope would be the name of the plugin folder. ex. fix(noice-nvim): fix LSP handler error

• Pull request title has the appropriate conventional commit type and scope where the scope is the name of the pre-existing directory in the project as described above

• README is properly formatted and uses fenced in links with <url> unless they are inside a [title](url)

• Proper usage of opts table rather than setting things up with the config function.

[TheSast]

Did you mean: "Make which-key entries color blue, as they should be" ?

[owittek]

LGTM

[RayJameson]

Did you mean: "Make which-key entries color blue, as they should be" ?

yea, my bad :D