Modules may end up calling clientReply directly in routeQuery

The way the routing currently works is that the client protocol's expected response count is incremented before the call to routeQuery is done. This avoids the problem where the response count goes negative if a call to clientReply is done inside the routeQuery call.

Modify the modules that do this to instead return it after the function has finished. Mechanisms for this are already available.