Change set_stream_logger to set logger at DEBUG

The issue is that in some situations, we weren't getting debug logs
from botocore or the CLI.  The issue is that by setting the stream
logger to a level of ERROR, we'll never get any debug logs emitted.

This change sets the logger to have a level of DEBUG, but leaves the
associated StreamHandler to have the associated level that's been passed
in.  This should result in no noticeable changes (`--debug` still has
the same result), but this has the benefit that you can add addtional
handlers that record at the DEBUG level (say in a plugin).

This particular situation was noticed because when a test fails, nose
normally captures all the log messages, which is helpful in diagnosing
what went wrong.  However, because clidrive calls set_stream_logger with
a level of ERROR, nose's log handlers can't capture any debug logs.
Merge branch 'fix-debug-logs' into develop

* fix-debug-logs:
  Change set_stream_logger to set logger at DEBUG
Split reset_method into two separate methods

One that checks for redirects and one that actually resets
the stream.
Fix indentation pep8 issue
Reset the stream on retry

When we retry a request, we first need to rewind the stream
if possible.  Otherwise, we will only send a portion (or none)
of the stream which will cause the server to wait because our
content length won't match what we've sent.  Eventually the server
will just close out the connection.

Fixes aws/aws-cli#401.
Debug log the reasons we're trying a request

No functional change.
Fix type in comment
Merge branch 'cli-issue-401' into develop

* cli-issue-401:
  Fix type in comment
  Debug log the reasons we're trying a request
  Reset the stream on retry
  Fix indentation pep8 issue
  Split reset_method into two separate methods