provide async features

[Emilgardis]

A feature for hooking into a async environment should be added. This is intended to make querying the is_dirty functions easier, eg. don't poll manually, use await.

This should also ensure thread safety for the functions that "need" to be run on the same thread. I need to figure out what happens if they are not ran on the same thread, and then figure out a way to solve it.

I think the easiest way to solve this is a static in each method, this static stores the thread it was first ran in, and panics/errors if it is run elsewhere. A possibility for this is to then also enable "resetting" the thread id. There has to be prior art for this right? :3

[Emilgardis]

Maybe the "one thread only" functions can take a &mut NotSendButSync where NotSendButSync: !Send + Sync

T: Sync iff &T: Send, but I dont think the same holds for &mut. Then we can ensure same threadedness (I think)