Add tokio bindings

[danieldg]

Fixes #20

[acheronfail]

@danieldg while I love the idea of upstreaming this awesome tokio PulseAudio mainloop into libpulse_binding, would you be open to publishing a separate crate for others (like me!) to be able to depend on it and use it?

From my perspective - and correct me if I'm wrong @jnqnfe - this crate seems to be more of a 1:1 binding between PulseAudio's APIs rather than "a bunch of rust tools and integrations for PulseAudio". So to me, a separate crate makes sense for what is essentially "a tokio implementation of a PulseAudio mainloop".

TL;DR: I would love it if the libpulse-tokio crate added in this PR could be published to crates.io. Whether that's by upstreaming here, or by publishing it separately.

[danieldg]

@acheronfail - I just published the current version of this branch. While it still has a few limitations, those can be fixed in future versions. I'd be open to adding the maintainers here to the crate if it was merged, so it could be maintained/released in lock-step.

[MaxVerevkin]

I just published the current version of this branch.

On crates.io? I couldn't find it.

[danieldg]

https://crates.io/crates/libpulse-tokio

[MaxVerevkin]

Thank you, I don't know why neither crates.io nor lib.rs could find it :(

[acheronfail]

@jnqnfe I was wondering if it'd be possible for this to be added to libpulse-binding?

I've been upgrading my dependencies, but upgrading from 2.28.2 to 2.30.1 actually means that @danieldg's libpulse-tokio breaks. 😢

Would be nice to have this all included in libpulse-binding itself. I can't remember if there was anything specific from blocking this?