STASHDEV-7788 Remove the code to timeout remote operations on the remote node

STASHDEV-7788 Remove the code to send CallTimeoutException responses
from remote operation threads back to the caller to indicate timeout.
These are expensive to deserialize (especially when the contents of
the CallTimeoutException are not used for anything anyway), and when
the queue is long can lead to an indefinitely growing queue of retried
invocations.
The whole premise of this test, that an indefinite `lock` operation should be interrupted with the call timeout, is completely wrong, and illustrates the confusion over what the "call timeout" actually means in Hazelcast.  I changed this test to the closest equivalent: a `tryLock` with explicit timeout.