Summary

This change adds proper macOS Command key support while preserving Control as a distinct physical key. It introduces a logical KeyboardKeys.Shortcut modifier, which resolves to Command on macOS and Control on other platforms, and updates editor default shortcuts to use that logical modifier.

Motivation

Previously, macOS Command was treated like Control in several places. That made common editor shortcuts such as Command+C/Command+V unreliable and also made it impossible to distinguish physical Control from Command. On macOS, these keys have different meanings: Command is the primary application shortcut modifier, while Control remains a separate modifier used by text editing and other workflows.

What Changed

• Added KeyboardKeys.Command for the physical Apple Command key.
• Added KeyboardKeys.Shortcut for platform-default application shortcuts.
• Resolved Shortcut centrally in input queries:
  • macOS: Shortcut -> Command
  • other platforms: Shortcut -> Control
• Updated editor default bindings from Control-based shortcuts to Shortcut-based shortcuts.
• Updated shortcut display code so menus and tooltips show platform-friendly labels.
• Updated input binding capture so pressing the platform shortcut key stores Shortcut rather than a physical Command/Control binding.
• Fixed macOS text input so Command combinations do not also insert text characters.
• Updated text box handling so editor-configured bindings are respected, and Command+Backspace follows macOS text editing behavior.
• Fixes a macOS-specific stuck-key case for Command shortcuts.

Notes

This does not migrate existing user settings. Existing customized bindings remain as-is, while reset/default settings use Shortcut.

Physical Control still means Control on macOS. A user can explicitly bind Control+C/Control+V (for example), and those bindings will not be treated as Command+C/Command+V.