use globs for input config

[Leon-Plickat]

implements #741

[Leon-Plickat]

Whoops, didn't see #819

I think this one is a bit more straight-forward though. Multiple configs matching an output is implicitly supported

[ifreund]

This approach of storing the glob directly in the InputConfig seems good.

The one thing I think needs more consideration is the handling of multiple globs matching a single input device and the order in which the the configs are applied.

I think we should keep the list of input configs sorted by generality of the globs just as we do with the RuleList abstraction. When a new config is added we would then do the following algorithm to apply configs to input devices:

for each input device:
    for each input config from most general to least general:
        if config glob matches device:
            apply config to device, possibly overwriting more general config

Does that make sense to you? We would also need to document this behavior in the man page.

[Leon-Plickat]

I was initially going to leave input configs in order of declaration, but ordering by generality does make more sense on second thought.

[ifreund]

LGTM, Thanks!