async-std support, second try

[yu-re-ka]

Unlike the first try, this does not rely on mutually exclusive feature flags. Both runtime-async-std and runtime-tokio features can be enabled at the same time. The actual runtime used is chosen by the user when creating the endpoint.

This does not touch the synchronization primitives (still uses channels etc. from tokio, even when running under async-std), and thus keeps tokio as hard-coded dependency.

To-Do:

• Tokio socket read/write paths needs to go via the AsyncFdReadyGuard again, otherwise it breaks
• Fix windows / !unix compilation
• Deal with lint errors that are not fixed by cargo fmt (" error: very complex type used. Consider factoring parts into type definitions")

[yu-re-ka]

@Ralith do you think this is an acceptable solution?

[yu-re-ka]

CI passes 🎉

[Ralith]

Thanks, this looks much closer to what I had in mind! This touches a lot of stuff as written, so I haven't yet gone through it in detail, but here's some initial thoughts that might help trim things down besides.

[yu-re-ka]

@Ralith please have a look at the current state of #1346 and tell me if it addresses all issues you raised