Description
When a second (or greater) observer is added to a Query, that observer should be treated exactly as is the first observer: It should, immediately, receive the results of running the query.
I am not positive that the code doesn't do this. It may. If it does, by all means, just close this ticket.
I am labeling this as critical, because moving to LiteCore QueryObservers will cause current dev-tests to fail, on all platforms. We can comment them out / @Ignore them so it is not actually blocking implementation...