If resharding fails due to any error that is not user initiated (and hence user won't expect ReshardCollectionAborted), followed by config server step down + step up, we recover the abort decision at the newly elected config server by checking the state document and signaling the context holder to abort here. When doing this we overwrite the status as ReshardCollectionAborted here incorrectly thinking it is user-initiated. Note that the original status at the previous config server primary's ReshardingCoordinatorService is present in memory in this onError handler in code.

When checking if the context holder is aborted, we should additionally check if it was user-initiated and return the right status code.