Reintroduce failing `queue_disconnected_test` test

This test was 'fixed' in 82e7964dd58401ad3d7eecb3a55e3bd62b54747d, but
further changes will allow it to pass as-is.
Never use infinity request timeouts

As described in #156, there are several types of timeouts in the client.
The timeout that is generally provided as the last argument to client
operations is used to create timers which prevent us from waiting for
every on messages for TCP data (from gen_tcp). There are several cases
where this timeout was hardcoded to infinity. This can cause the client
to hang on these requests for a (mostly) unbounded time. Even when using
a gen_server timeout, the gen_server itself will continue to wait for
the message to come, with no timeout. Further, because of #155, we
simply use the `ServerTimeout` as the `RequestTimeout`, if there is not
a separate `RequestTimeout`. It's possible that the `RequestTimeout` can
fire before the `ServerTimeout` (this timeout is remote), but we'd
otherwise just be picking some random number to be the difference
between them. Addressing #155 will shed more light on this.
Use infinity gen_server calls

The server has its own timeout mechanism for receiving TCP data, so
infinity gen_server timeouts are sufficient, barring any unknown bugs
where the server would never reply. Some functions still accept
`CallTimeout`s, but they're ignored.
Deprecate or remove functions which use CallTimeout

* Functions that have been part of a tag and use `CallTimeout` are marked
deprecated
* Functions that are part of the 2.0 additions and haven't been tagged
* yet are removed.

See 5aa1ab0ba214d8ec5b595735cf3822c3a4e9c49d for an explanation of why
all gen_server:calls are now using infinity timeouts.
Merge pull request #156 from basho/feature/unify-timeouts

Unify timeouts