Add `raise_send_errors` flag to the base `Client`.
This indicates whether the client will handle or raise any exceptions encountered while sending to Sentry.
* The default value (False) matches the current behaviour in which the client handles the error.
* Setting this argument to True allows for the calling application to handle the exception and
  thus determine its own retry and backoff strategies.
If a SentryHandler's client is set with `raise_send_errors = True`, do not handle the errors in `SentryHandler.emit`.
Ensure that ThreadedHTTPTransport sends all pending messages at exit

A race condition in the ThreadedHTTPTransport exit hook meant that it was
possible for some queued messages to not be sent.

Rearrange the shutdown hook a bit to ensure that this cannot happen.
Merge branch 'master' into fix_async_sender_shutdown
Merge branch 'master' into fix_async_sender_shutdown
Added HTTPS and transport options support to Tornado transport
Merge branch 'raise_send_errors' of https://github.com/richg/raven-python into richg-raise_send_errors

Conflicts:
	raven/base.py
	raven/contrib/django/client.py
	raven/handlers/logbook.py
	raven/handlers/logging.py
	tests/handlers/logging/tests.py
Merge pull request #455 from robinhoodmarkets/tornado_https

Added HTTPS and transport options support to Tornado transport
Merge branch 'master' of github.com:getsentry/raven-python
Merge branch 'fix_async_sender_shutdown' of https://github.com/swiftserve/raven-python into swiftserve-fix_async_sender_shutdown
Minor stylistic changes