Select OrderBy is not stable if a non-unique column is used for ordering

[dannychenmsft]

If a non-unique column is used for ordering, compute returns the top N matches. But those can be out of order w/rt to a secondary sort ordering (ID column is implied for now). Merge assumes these are in order. This was made worse by parallel/cascading merges because now merges happen in arbitrary order instead of partition order.