Add smoke tests for datetime serialization
Merge branch 'release-1.6.5' into develop

* release-1.6.5:
  Bumping version to 1.6.5
  Update changelog
  Added support for inline parameter values
  Support for parameter objects and values
  [EMR] Add mutual exclusive validation on --use-default-roles and --ec2-attributes InstanceProfile options in create-cluster command
  [EMR] Add mutual exclusive validation on --use-default-roles and --service-role options in create-cluster command
  [EMR] Add Hue to create-cluster examples
Merge branch 'timestamp-smoke-tests' into develop

* timestamp-smoke-tests:
  Add smoke tests for datetime serialization
Add timestamp issue to changelog
Fix long line lengths in test case
Switch ec2 sec group tests over to assert_params_for_cmd2
Do not document deprecated options

As far as I can tell, this is a regression from the previous
versions of the AWS CLI, although this problem has existed for
a while now.

To summarize what's going on, if you look at the reference page
for the EC2 API of AuthorizeSecurityGroupIngress, you'll notice
that the params I've marked as _UNDOCUMENTED in this PR aren't
documented in EC2's docs:

http://docs.aws.amazon.com/AWSEC2/latest/APIReference/ApiReference-query-AuthorizeSecurityGroupIngress.html

The reason for this is that these params have been superceded by
the IpPermissions list, which can handle all the cases of the
deprecated args as well as allowing for specifying multiple
rules in a single call.

Now, for convenience, we added a customization a long time ago that
re-adds these deprecated commands, but internally maps them to the
IpPermissions list.

However, a while back, the customization in botocore that handled
removal of deprecated params was changed such that these arguments
were being surfaced again.  This made it confusing for customers
because there's now similar args:

* ``--cidr-ip`` vs ``--cidr``
* ``--ip-protocol`` vs. ``--protocol``
* etc.

and they are actually mutually exclusive.

This PR adds back that old behavior by not documenting the
deprecated params and also adds a unit test to verify these
don't show up in our documentation again.

This should make things much more clear for customers.
Add a requirements26.txt for unittest2

Avoids us having to specify the version of unittest2 in every CI
system/test tool we use.  They can all just -r requirements26.txt
and we have a single file to change as we bump the unittest2 version.
Add same tests for revoke-security-group-ingress
Merge branch 'py26-requirements' into develop

* py26-requirements:
  Add a requirements26.txt for unittest2
Merge branch 'remove-deprecated-params-ec2' into develop

* remove-deprecated-params-ec2:
  Add same tests for revoke-security-group-ingress
  Do not document deprecated options
  Switch ec2 sec group tests over to assert_params_for_cmd2
  Fix long line lengths in test case
Add ability for skipping undecodable filenames
Update Changelog
Merge pull request #1038 from kyleknap/decoding-errors

Add ability for skipping undecodable filenames
Parse --statistic-values values into a decimal type

This was failing the improved botocore param validation because
we were previously setting this value to a string.  We now set
this value to a decimal.Decimal to ensure we have a valid type
that will also pass the botocore param validation.

While I was in the code, I also updated the code to use the new
botocore CamelCasing from metric_data to MetricData.  There was
also some general test cleanup to switch the tests to
assert_params_for_cmd2.

Fixes #1036.
Add issue to changelog
Add kinesis issue to changelog
Merge branch 'fix-string-type' into develop

* fix-string-type:
  Add issue to changelog
  Parse --statistic-values values into a decimal type

Conflicts:
	CHANGELOG.rst

Closes #1039.
Update changelog with new service updates
Bumping version to 1.6.6