HotRod addressCache iterator shouldn't go remote

In the forum post, the stack traces show the topology update being sent back from the server to the client. However it is using a distributed iterator. This shouldn't happen as the addressCache is a REPL cache which should own all segments and thus the iterator shouldn't go remote at all and just operate on the user thread solely.