Check fromCallback cleanup behavior about streamly HOT 1 OPEN

There a few things to take care of in the sample code above:

1. Make the callback caller block if a queue threshold at the consumer is reached, so that the queue does not grow arbitrarily.
2. Use atomicModifyIORef' to ensure correctness when the second stream is evaluated from concurrent threads.
3. The callback is registered when the stream starts getting evaluated, so it may miss events from the source stream before that. That may or may not be ok depending on the use case.
4. In general, the consumer stream needs to remove the callback from the list of callbacks when it is done, though it depends on the specific use case. For that it will have to associate some id with the callback. The IORef can keep an id counter for that and we can store a (id, callback) tuple.
5. Exceptions in the consumer streams cannot be propagated back to the source stream.

from streamly.