Readability improvements to SortShuffleReader

Some of the changes include:
* Changed ioSortFactor to maxMergeWidth to clarify what it means.
* Changed "partition" to "block" to avoid confusion with Spark's more typical use of the word partition.
* Added header documentation.
* Rearranged and documented the main merge loop.
Yes, I think so. I think we should judge whether memory is enough firstly, then put to `memoryBlocks` if enough, otherwise directly spilling to disk.