Don't fail fast when service is unavailable

When a client attempts a N1QL query (for example) against a cluster that does not have the Query service enabled, the client will fail-fast and throw a ServiceNotSupportedException. However, in some situations, this not the ideal solution - for example, if there is a single query node and it is failed over or swapped out this will lead to the client throwing exceptions when the better path is probably returning the exception as the IResult.Exception value. This will allow the client to recover during temporary downtimes.