ARM does not send a `killCursors` request only when we are absolutely sure that the shard cursor has not been already killed. We identify that by looking at the error code in the status of the cursor. We should improve this approach either by formalising an error category and label to indicate cases where the cursor is guaranteed to already have been killed, or by dynamically attaching extra error info in cases where the cursor is destroyed.