Merge branch 'release-1.3.4' into develop

* release-1.3.4:
  Bumping version to 1.3.4
Update changelog with 1.3.4 release notes
fix table output for multibyte characters

Encoding unicode text with `str` does not work
for multibyte characters.
Update session to use single loader instance

Reduces memory bloat when running tests, which is causing
issues on some test systems.
Merge branch 'cache-loader' into develop

* cache-loader:
  Update session to use single loader instance
Merge branch 'quiver-support-unicode-row' into develop

* quiver-support-unicode-row:
  fix table output for multibyte characters
Add changelog entry for #721
Use unicode escape sequence for file type
Use larger range of random digits to avoid collisions in test

Previous we had 5000 combinations, now we have 36 ^ 10.
Remove test with spaces

These will be part of another pull request.
Merge branch 'fix-windows-integ-test' into develop

* fix-windows-integ-test:
  Remove test with spaces
  Use larger range of random digits to avoid collisions in test
  Use unicode escape sequence for file type
Use unicode escape sequence for file type
Add integ tests for #718

The root cause was in botocore which has its own tests, but
this verifies that we can upload/download/sync files with spaces
as expected.  Depends on boto/botocore#264.
Bug fix for integ test on windows wiht py3

Subprocess expectes str() not bytes() and will try to process
the arg as a list if it receives bytes().
Merge branch 'issue-718' into develop

* issue-718:
  Add integ tests for #718
  Use unicode escape sequence for file type
Add s3 whitespace issues to changelog
Update changelog with S3 endpoint fix
Fix issue with shadowed max-items arguments

When we add pagination configs for a service, we hide
the original manual pagination arguments in favor of the normalized
arguments.  However, to support backwards compatability we still
allow users to specify the manual arguments.  If we detect this is the
case we will turn off pagination.

However, when the normalized argument matches the manual paging argument
(as is the case when a service users `MaxItems`), we have an ambiguous
case.  Did they mean the back-compat version of the normalized argument
version?  Previously we were assuming the user meant the manual paging
argument.  Now we assume that they meant the normalized paging
arguments.

Services impacted:

* route53
* iam
* ses
Fix failing test

We don't pass max-items anymore.
Merge branch 'page-args' into develop

* page-args:
  Fix failing test
  Fix issue with shadowed max-items arguments