rehashing inconsistency when eagerLockSingleNode enabled

When eagerLockSingleNode="true", if the main data owner of a key changes during a transaction then the k might end up in inconsistent state.
A solution to avoid this is:

• on topology change, if a eagerLockSingleNode is enabled, iterate over all transactions's keys
• if the main owner for a key has changed then just mark the tx for rollback

This way, on next operation for that transaction an exception should be thrown, e.g. TxRollbackOnlyException