feat(event): implement touchpad and touchscreen button translation

[nileshchakraborty]

When configuring custom device profiles with touchpad button mappings (e.g. Touchpad:RightPad:Touch:Button:Press -> Mouse:Button:Left), translations previously failed with Translation not implemented for profile mapping.

Changes

• Implement translate_touch_button() in src/input/event/value.rs to route Touch::Button events (Touch and Press) to mouse buttons, gamepad buttons, keyboard keys, and touchpad buttons.
• Add unit tests verifying touchpad and touchscreen button translation across target types.

Fixes #692

[nileshchakraborty]

Testing & Validation

1. Unit Tests (Fedora 44 container):

   • Added test_touchpad_button_translations() in src/input/event/value.rs verifying mappings from Touchpad(RightPad(Touch::Button(Press))) to:
     • Mouse(Button(Left))
     • Gamepad(Button(South))
     • Keyboard(KeyA)
     • Touchpad(CenterPad(Touch::Button(Touch)))
     • Touchscreen(Touch::Button(Press)) -> Mouse(Button(Right))
   • cargo test --all-targets passed (14/14 unit tests, 4/4 doc-tests).

2. Clippy (Fedora 44 container):

   • cargo clippy --all-targets -- -D warnings passed with 0 warnings.

[pastaq]

Please make a new file, value_teat.rs, for all unit testing.

[nileshchakraborty]

Done. Extracted all unit tests into a dedicated src/input/event/value_test.rs file and verified test execution.

[pastaq]

This is a bit of an anti-pattern but it does reduce nesting quite a bit. Probably a good direction for a refactor of older code at a later time. Not an ask, just making a note for myself.

[nileshchakraborty]

@pastaq is there an automation that merges the changes, as I dont see an option to merge the PRs.

[pastaq]

No, I'll do it when I'm ready to publish a new release.