ISPN-4696 SuspectException kills operation on ClusterRegistryImpl

* Added retry for ClusterRegistry operations

https://issues.jboss.org/browse/ISPN-4696

Note this is only a stop gap solution for the time being since we do not know yet how we want to fully handle nodes leaving during a commit.  At least with the ClusterRegistry we know we can easily retry the command.
This method might be useful for [ISPN-4717](https://issues.jboss.org/browse/ISPN-4717), since it makes it easier to detect a SuspectException in the stacktrace. 

BTW, this is important. When working on dealing with suspect exceptions in HR client, I discovered that sometimes you get a JGroups' SuspectedException as opposed to a SuspectException... To be more precise, handling JGroups' exception was added as part of [ISPN-1929](http://issues.jboss.org/browse/ISPN-1929)