Logging an exception instead of / and a `raise` pollutes the log with extra traceback.

### Problem:

In many places in the SDK codebase, there are exception logging using the `_LOGGER.exception`. This logs the traceback of the exception. The encountered exception might then be bubbled up to the caller, or to the exit call which then again logs this exception. This causes duplicate logging at best, and confusion at worst since the exception message/type can be different.

### Solution:

Clean up the logging, and use raise over logging the exception wherever possible.

Ref https://github.com/aws/aws-encryption-sdk-python/issues/566

[//]: # (NOTE: If you believe this might be a security issue, please email aws-security@amazon.com instead of creating a GitHub issue. For more details, see the AWS Vulnerability Reporting Guide: https://aws.amazon.com/security/vulnerability-reporting/ )

Search the SDK codebase for uses of `_LOGGER.exception` and review the related issue #566 for context. Trace whether each exception is bubbled up to a caller or exit path that logs it again; done means redundant traceback logging is removed while the exception still reaches the appropriate caller.

Written by the indexing model from the issue text.