#802 added additional checks if hard exceptions occur in IConnection (not only faulted tasks, synchronous version was ok but async version did not failover properly
added unit tests where the sniff endpoint throws a hard exception in IConnection
added tests for hard exceptions in IConnection async methods
Improved exception messages to include ping/sniff exceptions more clearly as suppose to inner maxretry exceptions. Added integration tests for the exception (which behave different in practice then theory (unit tests
fixed failing unit test in because I tried to see if picking a random nodeif all the nodes are dead over picking the one thats dead longest would work better in practice
fixed async exceptions bubling appropiately
Wrote more unit tests that check wheter .ServerError is properly set. Works in unit tests not in integration tests..
fixed error responses that exceeded 65kb being truncated (sigh WebRequest) causing ElasticsearchServerException to throw a nullreference and .ServerError to always be null
Show stacktraces in MaxRetryException message
fixed failing unit tests
ignored startup tests for now
fixed mono builds and made sure the HttpConnection changes do not affect Mono
updated test that succeeded because fiddler was running
Fix casing
Merge pull request #803 from elasticsearch/fix/hard-exceptions-connection-failover

Failover broken when hard exceptions occured when using *Async  methods