Fix MS ordering bug in MultiMSReader
The multi-MS reader reorders the MSReaders without reordering the ResultSteps with it. Best case, it produces a crash, as reported by Bharat and Alexander. Worst case, it moves visibilities to the wrong frequency.
It looks like this bug was introduced in !889 (merged).