Locking interceptor should check the topology before acquiring locks

The distribution interceptors check the command topology is the same as the current topology before sending a command to remote nodes, but the locking interceptors do not have any check.

On a remote node, this means the inbound invocation handler acquires some locks in topology T, then the locking interceptor acquires other locks in topology T+1, and finally the distribution interceptor throws OutdatedTopologyException and releases the locks. In older versions there is also a potential for blocking a remote executor thread while waiting for the lock, but luckily that is not a problem in 9.4+. It would be more efficient if the locking interceptor was throwing OutdatedTopologyException instead.