[feat]: Overhaul shortcuts and actions

[fallenleavesgocrunch]

Problem / motivation

It's a little too easy to accidentally do a thing if you press the wrong key

Proposed solution

This is going to be controversial. I've been using lfk for most of the projects life... the keybindings are kinda crazy.
I don't have all the answers here but what I'd prefer is casual key presses to do a filter on whatever the center list is and control+ allows alternate navigation than arrow key drilling down, while control+shift+ is for potentially destructive actions like create, edit, delete.

A leveled consistency in all views would be a good thing; it seems like most views have special cases. I know LLMs are used heavily in this project and that explains why it's all special cases instead of general functionality. It's worked incredible well and there is a plethora of capability now.

Alternatives considered

I did consider a fork, but then I thought I might as well raise the idea to see what you think.

Area

Navigation / layout

Additional context

No response

Pre-flight checks

• I searched existing issues and did not find a duplicate.

[nikaro]

May be use read_only: true and toggle to "write mode" only when needed. That's what i do.

[tsacha]

I think the project has too many keybinds for rarely used features.

A command palette like VS Code's could be a good solution to keep daily navigation simple while still allowing quick access to advanced actions. Using the : command input for this doesn't feel very accessible.

Tools like the API explorer, Object explorer, RBAC browser, or monitoring view are great, but having direct keybinds for them adds unnecessary complexity to lfk.

Additionally, features like the color picker, color scheme, or terminal mode could simply be configured in the config file rather than requiring dedicated keybinds.

What do you think @janosmiko ? I'd be curious to hear your vision on this topic.