[8.x] Remove ksort in pool results that modifies intended original order

[lukeb]

Bug Report: #37774

[taylorotwell]

Why do they need to be in the same "order"... it is an associative array so they should be accessed by their named keys anyways?

[lukeb]

While this was a simplistic example for the bug report, there are more complex use cases that use the as('string') method and yet still should retain the originally intended order in the results. There is no reason to reorder them.

For our case, we're importing large numbers of real estate listing photos. When the pool requests complete, we're piping the collection through additional map() callbacks and it must maintain the photo order the listing agent desires.

Removing the ksort doesn't change anything with numerically keyed array of requests either. Ultimately, ksort isn't necessary.