Forking to deviceplug/btleplug (until this possibly goes unabandoned?)

[qdot]

As much as I really don't want to do this, I'm getting the feeling that rumble has been abandoned, so:

I've forked rumble over to https://github.com/deviceplug/btleplug

We need an updated library version to update https://github.com/buttplugio/buttplug-rs on crates.io. I've brought in a few of the pull requests here, as well as building out our own patches to fix up WinRT support, and will be starting MacOS CoreBluetooth support soon (Update: As of 0.4.0 we now have Linux/MacOS/Windows 10 UWP).

My plans include:

• Reworking the API a bit to make it reflect something other than bluez (collapse central/adapter, route device connect/disconnect events through device objects instead of having to deal with the central for everything, etc..), as working with it right now is kinda painful.
• Shore up cross-platform support (probably by cribbing off https://github.com/akosthekiss/blurmac and maybe poking @geovie for help for MacOS, may try adding Android support via also cribbing off other Servo WebBluetooth impls if I'm feeling zany)
• Probably get it CI'd through Azure Pipelines

I will reiterate that I really don't want to do this (I seriously do not have time to support a full Bluetooth library), but this is the Rust library with the most development on it so far and I'd really rather not start from scratch. I'm not doing this out of animosity by any means, and am completely up for sharing patches or un-forking if that becomes an option. I'll be keeping the licenses MIT/Apache, and excluding this from the other licensing/CLA requirements of the other orgs I run.

If anyone wants to help out, or there are any objections, please let me know.