Merge branch 'release-0.70.0' into develop

* release-0.70.0:
  Bumping version to 0.70.0
  Update services
Only set auth_path once, fixes signing errors

Fixes aws/aws-cli#986

The bug was that the fix_s3_host always sets the auth_path
to the current path of the request.url.  However, in the case
of a retried request, we call fix_s3_host again which changes
the auth_path to the (already modified) request path.  This
generates an auth error.

The fix now is to check if auth_path is set, and if it is, then
we can immediately return.
Update cred provider to have more general date parser

Also, the default time fetcher now returns time zone aware
local time.  This results in no external function change,
but it does allow for more generalized date string formats
to be provided (it uses dateutil.parser.parse() to parse
timestamps now).
Remove unused import
Merge branch 'fix-retry-auth-error' into develop

* fix-retry-auth-error:
  Remove unused import
  Only set auth_path once, fixes signing errors
Cleanup test_credentials formatting

* pep8
* remove unused imports
* remove unused vars
* adding missing assertion to a test
Revert "Merge branch 'fix-retry-auth-error' into develop"

This branch is failing multiple S3 integration tests and needs
investigation.

This reverts commit 791cfdcf8dd08ded1b65e2dfd5d684aa2fddea0a, reversing
changes made to e754fc0d7b4a51dc1ac11c8fc5916873ce458526.
Merge branch 'tz-aware-cred-refresh' into develop

* tz-aware-cred-refresh:
  Cleanup test_credentials formatting
  Update cred provider to have more general date parser
Move auth_path handling to the request.

This fixes the previous issue where this was not fixed
previously by checking if the auth_path was not None.
By moving the handling of the auth_path onto the request
itself, this makes is easier to ensure that the auth_path
manipulation only happens on a per request basis.
Merge branch 'fix-retry-auth-error' into develop

* fix-retry-auth-error:
  Move auth_path handling to the request.
Allow idempotent request signing

This fixes a bug where request signing is not
idempotent.  This is because setting a header
value does not replace the old value, it actually
appends the new value to a list of values associated
with the header name.  This causes issue when the
same request is retried, particularly with S3 retries.
Use v2 version of the waiter model

Looks like there was an error when pulling the latest models.
We should be using the v2 models of the waiters.

cc @kyleknap
Add get_waiter_model to session object

Similar to get_service_model
Merge branch 'fix-auth-resign' into develop

* fix-auth-resign:
  Allow idempotent request signing
Merge branch 'session-waiter-model' into develop

* session-waiter-model:
  Add get_waiter_model to session object
Bumping version to 0.71.0
Merge branch 'release-0.71.0'

* release-0.71.0:
  Bumping version to 0.71.0
  Add get_waiter_model to session object
  Use v2 version of the waiter model
  Allow idempotent request signing
  Move auth_path handling to the request.
  Revert "Merge branch 'fix-retry-auth-error' into develop"
  Cleanup test_credentials formatting
  Remove unused import
  Update cred provider to have more general date parser
  Only set auth_path once, fixes signing errors