Use only exceptions in the routing API

The routing APIs have been steadily moving towards using exceptions to return fatal errors for situations where the whole session must be torn down. The reason for using exceptions is that the context of the error is clearer at the exception handling site which makes for better error messages.

As a final cleanup, the routeQuery() and clientReply() calls should be modified to have no return values.