Corrupted shuffle transfers to disk are not detected during transfer

When a shuffle transfer is larger than the single transfer limit it gets written straight to disk during the transfer. Unfortunately there are no checksum validations performed during that transfer, so if the data is corrupted at the source or during transmit it goes undetected. Only later when the task tries to consume the transferred data is the error detected, but at that point it's too late to blame the source task for the error.