Updated to the latest libPusher release/1.5 branch.
Ignore xccheckout files
Change project whitespace settings to match actual whitespace.
Clients no longer connect automatically.
Handle disconnections/failures due to network failure (where the Pusher
client will not automatically handle the reconnect) by waiting for
reachability to change and then manually reconnecting.

If connection fails and we do have reachability, then just reconnect
immediately.
If we disconnect with a PTPusherErrorDomain error and reconnect = NO,
it means we got a 4000-4099 error code which means we never want to
reconnect.
Limit the number of manual reconnects we attempt before giving up.
Refactor disconnection handling by extracting to a new class that could
potentially be re-used outside of the diagnostics app.

I wanted to limit the dependencies to just the PTPusher instance and
Reachability, so I've kept logging outside of the class by using a
delegate to notify of significant events and leaving the logging in
the view controller.
Updated code comment
Just safeguarding against a potential (albeit unlikely) race condition.
Backported race condition fix.
Apps using libPusher should enable UIRequiresPersistentWiFi.
Updated Pusher podspec to use correct header path
Updated to latest changes on libPusher branch.
Reflect the changes in auto-reconnect behaviour.
Updated Pods to use release version of libPusher 1.5.
There are a few minor warnings in the tagged build of SocketRocket which
we can safely ignore.
Check the more specific error domain
When handling disconnection manually, if we do seem to have reachability
then try again after a short delay as recommended in the libPusher
README.
Don't connect until we have initialised everything.