🧪 [testing improvement] Add robust unit tests for eventToShortcut

[beingniloy]

🎯 What: The testing gap addressed

The utility function eventToShortcut in src/utils.ts was completely untested. This function normalises KeyboardEvent data into normalised string representations of keyboard shortcuts like "Ctrl+Shift+S". Also corrected a small discrepancy where the function was outputting "Control" instead of "Ctrl", matching the rest of the application's expected format.

📊 Coverage: What scenarios are now tested

Implemented 15 unit tests covering:

• Single lowercase/uppercase character keys and numeric keys without modifiers.
• Adding single modifiers (Ctrl, Shift, Alt, and equivalence of metaKey -> Ctrl).
• Combining multiple modifiers in the correct join order (e.g., Ctrl+Shift+Alt+P).
• Correct translation of keys from KEY_SHORTCUT_MAP (e.g., punctuation, Space, Escape, and Arrow keys).
• Suppression/returning empty string for modifier-only keys (e.g., Control, Shift, Alt, Meta).
• Correctly handling multi-character keys not in the mapping (e.g., Enter, Backspace, F11, Tab).

✨ Result: The improvement in test coverage

Significantly increased reliability of the keybindings system by providing 100% path and branch coverage of the eventToShortcut function, safeguarding keyboard shortcut registration and processing from regressions.

---

PR created automatically by Jules for task 5523296383699020465 started by @beingniloy

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.