feat: Gesture configuration backend

[ryanabx]

This is an implementation of a backend gesture configuration based on a gist I made a few weeks ago: https://gist.github.com/ryanabx/e18b70d58f651c1a6946a5bca7a11165

This method of configuration would allow the frontend settings to do whatever they'd like with the gesture configuration without having to do something complex (unless they wanted to!)

Basically, gesture configurations are split per finger count and can be one of two types:

• Workspace dependent (depends on the direction of workspaces (horizontal/vertical) (for example, workspace switching gestures would need to be workspace dependent)
• Directional (doesn't depend on the direction of workspaces) (for example, window focus switching gestures need to be workspace independent)

to-do:

• configurable gesture implementation in the input module
• config item for touchpad gestures
• default configuration for touchpad gestures (I don't know how to do this, advice needed)

[ryanabx]

Rebased to include the RWLock changes. @Drakulix can you look at this at some point? I think this is a good direction to go for gesture configurations but I need to know if you and others agree

[Drakulix]

Do we really need another enum for this? We already have the Action-enum that is used for key-bindings. Can't we just use that and special case some actions like NextWorkspace/PreviousWorkspace when using gestures? (To animate those properly.)

That would make configuration much more flexible and allow binding more things to gestures.

[ryanabx]

Sure, I'll look into doing that

[ryanabx]

After looking into it, I'll hold onto this PR until #400 is finished, because it moves the Actions enum into cosmic-comp-config, where I need it