**Problem Overview**  
Currently, most keybinds in Omarchy are defined in the default configuration files, which get reset or overwritten every time `omarchy-update` is run (or at least requires you to git reset before running it). This makes it difficult for users to customize keybinds persistently, as changes to defaults are lost on updates. It would be great to migrate these to user-level config files (in `~/.config/hypr/`) so users can override them without workarounds.

Any workarounds used by the user to change default bindings will also result in needing to workaround the 'Hyprland Keybindings' overlay with SUPER+K.

**My Specific Use Case**  
I use a 75% keyboard that lacks a dedicated PrintScreen button. Instead, I've remapped the 'END' key (or sometimes a function key) to handle screenshots. To make this change, I either have to:  
- Implement hacky workarounds at the user level (e.g., additional scripts or overrides that might conflict).  
- Edit the Omarchy defaults directly, which get wiped out on every update, forcing me to reapply changes repeatedly.  

This isn't ideal for accessibility and customization, especially for non-standard keyboards. Moving keybinds to a user-editable layer would solve this and make Omarchy more flexible for diverse setups.

Of course I could just make `~/.config/hypr/hyprland.conf` source my own bindings file and `omarchy-show-keybinds` script (i actually did do this), but i'd rather it be native Omarchy.

**Proposed Solution**  
- Relocate default keybinds to a structure where users can easily override them (e.g., via a `user-keybinds.conf` file that gets sourced after defaults). 

Happy to work on a PR if agreed upon.