Compilation error on macOS. Quick fix.

The depth is locked to max:20

The Lapis is doing something odd where it's not recieving notifications
on Windows: meaning DeviceType isn't usable. Instead the device name is
used as a fallback (using a regex)

Lapis "works" with Lovense Connect, except that I can't get the Vibrate3
command to work, so it;s just giver/receiver vibes when connected this way.

I'm struggling to get them to pair, bit otherwise this should work.

This chipset appears to be able to pair with Satisfyer devices (on Windows 11), but
the connection can't be establisted from buttplug (it does appear to trigger the OS
connected state though, so I'm suspecting the limitation here is the same as the
Intel BT5 chipset and more related to the Windows stack than the hardware)

Some of these devices have connectivity sensors, some have IR LEDs and some
have estim, but none of that's mapped out: just the basic vibe operation.

Note: these devices are almost as bad as fire and forget RF. We're tracking our
assumed state of the device and updating the speed based on what amount to hitting
the speed up/down buttons. Id the device was previoulsy connected, it may already
ben in the "powered on" state, in which case out initialiser will change the state
to off (the device will beep twice) but we won't know and it'll be up to the user
reset the device (or restart the connection somehow).

* Solstice X
* Zenith
* Xone

Add Async HID Manager and Switch Joycon/Pro Gamepad support. This was
mostly written 2 years ago but that code is old enough that I basically
ended up having to rewrite it.

Uses code from a gist and from joycon-rs (so we can just wired things
through our own HID manager instead of using their impl), need to
update license.

The package bringing the library in can define the runtime type, we
don't really care.

Removes unneeded block_on calls, and we don't call tests in WASM
contexts so just defaulting to tokio runtimes is fine.