There's a closed pull request on the void-packages repository

New package: ydotool-0.2.0
https://github.com/void-linux/void-packages/pull/31237

Description:
It seems like the package uses CPM in its CMake config for statically linking `libevdevPlus` and `libuInputPlus`, both are versioned newer than the existing ones in Void, with breaking changes. There's another dependency called `IODash` which doesn't exist in Void yet.

Is it OK to simply use CPM? Or should we update the first two and add the last one into Void, then build with those? Pinging @steinex for opinions.

We already have #25341, but it's an older version and apparently have some unfixed problems... So I wish this is a friendly takeover of that PR.

closes #31163

<!-- Mark items with [x] where applicable -->

#### General
- [x] This is a new package and it conforms to the [quality requirements](https://github.com/void-linux/void-packages/blob/master/Manual.md#quality-requirements)

#### Have the results of the proposed changes been tested?
- [ ] I use the packages affected by the proposed changes on a regular basis and confirm this PR works for me
- [ ] I generally don't use the affected packages but briefly tested this PR

<!--
If GitHub CI cannot be used to validate the build result (for example, if the
build is likely to take several hours), make sure to
[skip CI](https://github.com/void-linux/void-packages/blob/master/CONTRIBUTING.md#continuous-integration).
When skipping CI, uncomment and fill out the following section.
Note: for builds that are likely to complete in less than 2 hours, it is not
acceptable to skip CI.
-->
<!-- 
#### Does it build and run successfully? 
(Please choose at least one native build and, if supported, at least one cross build. More are better.)
- [ ] I built this PR locally for my native architecture, (ARCH-LIBC)
- [ ] I built this PR locally for these architectures (if supported. mark crossbuilds):
  - [ ] aarch64-musl
  - [ ] armv7l
  - [ ] armv6l-musl
-->