ISPN-4696 SuspectException kills operation on ClusterRegistryImpl

* Added retry for ClusterRegistry operations

https://issues.jboss.org/browse/ISPN-4696
I still believe that this is the wrong way to solve this: a SuspectException should be handled and swallowed by the transport code. If we, and, even worse, our users, have to defensively code against SuspectExceptions it is definitely a usability problem.