Let ResultConjunctFuture return future results in same order as futures

The ResultConjunctFuture should return future results in the same order as the futures were specified. The advantage would be that we maintain the same output order as the input order if the input has been specified with a special ordering.

This should also fix a current performance regression where we don't maintain the topological ordering when deploying tasks. Due to this, we need to make an additional result partition lookup which adds additional latency. The problem has occurred due to FLINK-10431 which changes the interleaving how the slot futures are completed.