Hi Acsandmann,

Thank you for your hard work on rift, excited about the idea behind this project and i look forward to including this more in my developer workflow.

Hopefully this PR is helpful.

This PR makes the, most notably, toggle-activated action available via the CLI. In addition, it makes all actions that are currently only accessible via configuration-based keybindings available via subcommands in the CLI. After these changes the following subcommands will be available:

# Toggle whether rift manages the current macOS space
rift-cli execute space toggle-activated

# Switch to an adjacent macOS space (left, right, up, down)
rift-cli execute space switch left

# Focus a specific window by its internal ID (pid:idx format)
rift-cli execute window focus-id --window-id 1234:1

# Print layout tree to stdout for debugging
rift-cli execute debug

# Print serialized engine state to stdout for debugging
rift-cli execute serialize

in my mind there are two main benefits to this

1. for folks like me who are attempting to use karabiner exclusively (or another key mapping tool) for interacting with rift - this removes the need to have keybindings defined for both rift and karabiner.
2. if anyone decides to use the rift-cli exclusively, they can avoid having to add rift to the "input viewing accessibility settings" in mac os x system preference.

I hope these changes find you well
~Nick