Policy-sentry

In the last version, if you specified "tagging" in your YML file, the write-policy command was ignoring it. This fixes that.

* database: Fixes 51 - Give the user an error when the database file does not exist (in connect_db function). Except for the case of the initialize function.
* query: The query command now supports querying for wildcard only actions at an access level per service. For example, the only wildcard-only action under S3 at the Permissions management access level is s3:PutAccountPublicAccessBlock
* query: The query command now supports yaml output. This Fixes 95 (output in the Query command) but does not fix 11 (since 11 is asking for the write-policy command to support YAML, and was before the query functionality came out).
* query: the get_actions_matching_condition_key_crud_and_arn is available. This provides some scaffolding for 21
* travis: Auto-deployment of Python package with TravisCI

get_actions_with_access_level` now supports 'all' so you can query literally all IAM actions that have Permissions management or other access levels

* Template:
- `arn` is now `role_arn` to avoid confusion when writing templates
- `tag` is now `tagging` to avoid inconsistency when writing templates
* `write_policy_with_actions` `write_policy_with_access_levels` can be called directly.
* `get_crud_template_dict` and `get_actions_template_dict` are available so developers can create the templates by calling the library. They can pass that into write_policy_with_actions and write_policy_with_access_levels
* Added examples for the above in the docs

Previous one was oversized and had some stale actions.

* Docker support
* Write-policy allows template via STDIN
* Better JSON Schema validation
* Fixed an issue with the pre-bundled DB path from 0.6.4.