Pessimistic tx write on a non owner should consolidate LockControlCommand and ClusteredGetCommand

Today when a write occurs in a pessimistic transaction it must first lock the key for that entry. If the node is not an owner it may also retrieve the previous value, given Flag configuration. This leads to sending 2 requests when we could instead consoldiate this to do a single ClusteredGetCommand with the FORCE_WRITE_FLAG which would both retrieve the value and lock they key.