Perform write consistency check on node that holds primary shard instead of the node that receives the request

Oh , I see. This is a protection against recursion during a last attempt we do on timeout, where the timeout flag is set (isTimeOut doesn't actually check for timeouts). This pattern smells (and is probably my fault, if I didn't take over an existing pattern) but I'm worried this change is no good? (and we need a comment explaining why).