Consider making waker_set its own crate

I think the waker_set implementation is useful in it's own right. At the very least futures-util has something very similar and could probably benefit from sharing the waker_set implementation between the crates. It also may be useful in implementing other synchronization abstractions or combinators that need to keep track of a list of tasks to notify.