Indexing remote nodes should not attempt to do so using transactions

When running in a cluster with index storage configured locally for each node, changes in the cluster are reflected in the indexes via events sent by JGroups which are then processed locally on each node.

The processing of these events (the actual node changes) should not be done in active transactions - by starting and committing transactions - because they are not part of cache operations.