Migrate ec2inventory plugin to use boto3

[Migrated]

The upgrade to Boto3 is part of an ongoing initiative of having a single instance which coordinates deployments - with support for automatic deployments in pre-production environments.

Boto3 has built-in support for the default AWS Credentials Providers stack.

We need to set the cross-account trusting policies for our accounts, being then able to specify automatic role assumption in a cross-account context via ~/.aws/config.

It might now work out of the box, as it doesn't for aws-cli (see: https://github.com/aws/aws-cli/issues/1604 and https://github.com/aws/aws-cli/issues/1390).
In that case, we would need to do programatic role assumption - I was not been able to fully test this yet (permissions).

Note
This change is intended to be backward-compatible with the current setup - in other words, temporary/static credentials should work as before.

Locate the ec2inventory plugin and trace its current AWS credential handling first. Check whether boto3's default credentials provider supports the stated cross-account setup, then assess programmatic role assumption if needed; done means preserving temporary/static credential compatibility while enabling the intended configuration.

Written by the indexing model from the issue text.