revisit [no connection] error logic

[Sam Griffiths]

currently the bot wil detect no connection to the exchange, try for a further 60 seconds and then halt with notifications the issue is that with no connection, the halt command to clear orders won;t be received by the exchange which could lead to arbitrage against the bot.

added to that is the fact that a restart will clear the connection issue indicating that the bot may be getting stuck in the no connection state and not reporting a good connection correctly.

needs investigation before logic can be revisited. in the meantime a notification is sent and a restart fixes the issue. hence moved to 0.1.5 milestone

[Sam Griffiths]

I have added a conditional statement to the gracefulQuit method in sendLiquidityTask.java
this conditional checks if there is currently connection to the targeted exchange.
if there isn't the bot assumes a general connection issue and notifies of such via log, hipchat and email.
importantly it then rests the internal timer to allow for more time to regain connection rather than shutting down.