Expose result_keys as a property

Allows clients to manually construct the results if they want
to do so.  Used by the CLI.
Update botocore to use dev branch of jmespath

This also required a change to the s3 page configs.  Based
on feedback, the 'or' token was replaced with '||'.
Update test with new 'or' jmespath syntax
Merge branch 'jmespath-or' into develop

* jmespath-or:
  Update test with new 'or' jmespath syntax
  Update botocore to use dev branch of jmespath
Merge branch 'expose-result-keys' into develop

* expose-result-keys:
  Expose result_keys as a property
Update EC2 model for Reserved Instances instance type modifications
Update opsworks models for new resource management features
Merge branch 'model-updates2' into develop

* model-updates2:
  Update opsworks models for new resource management features
  Update EC2 model for Reserved Instances instance type modifications
Bump jmespath dep to 0.0.3
Bumping version to 0.19.0
Merge branch 'release-0.19.0' into develop

* release-0.19.0:
  Bumping version to 0.19.0
Updating requests to 2.0.0.
Revert update to requests 2.0.0 because httpretty 0.7.0 is broken for Python 3.3.
Add a Content-MD5 header to s3api delete-objects requests.  Fixes https://github.com/aws/aws-cli/issues/400.
Adding a unit test.
Reintroduce the upgrade to requests 2.0.0

Should be good to go now that we don't need httpretty
in the CLI tests.
Merge branch 'requests-2.0.0' into develop

* requests-2.0.0:
  Reintroduce the upgrade to requests 2.0.0
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.