Handle mixture of keycombo/no action in pad rings/strips
If a tablet ring/strip gets a compositor action mapped in one direction but not the other, there would be some inconsistencies in how these events are handled:
- In the pad OSD, the action would become
None / None
(accounting for both directions), this is wrong since one direction does have an action associated. - The ring/strip events would be partially handled by the compositor and the Wayland client, depending on the direction these are triggered. All ring/strip events should be handled in a single place instead.