Policy-sentry

* Fix redshift:getclustercredentials override (132)
* Update overrides to include new resource based policies (EFS is new and worklink was not previously included)
* Docs refresh
* Fixed logging - now just specify `-v debug` instead of `--log-level DEBUG`

* **Breaking change** and **new**: Template is modified again. This allows easy additions of wildcard-only actions with access levels specific to services (such as "S3 actions at read access level that do not support resource constraints"), so you never have to look at individual IAM actions again.
* **New**: Output will be in UpperCamelCase rather than all lowercase, for human readability. Note that if `--minimize` is specified for `write-policy`, it will give me lowercase. Otherwise, it will be UpperCamelCase. Fixes 124.
* **New**: Terraform module - 112

This leads to less user errors - and helps me out with the improved terraform module.

* Quick fix for jlongman's issue with write-policy - 118
* Fix the overly verbose logs for 119

User-facing changes
* The `initialize` command is now completely optional.
* **Removed**: The `analyze` command is deprecated and removed. We moved this functionality over to Parliament [here](https://github.com/duo-labs/parliament/pull/66)
* **Removed**: The `download-policies` command is deprecated and removed.
* **Breaking change**: Template format is vastly different. You will have to either pin to an old version or update your templates.
* **Removed**: The `--crud` flag for `write-policy` command. Now users do not have to specify the `--crud` flag. Policy Sentry will automatically detect the format.
* **Removed**: `analyze` and `download-policies` commands.

Developer library changes
* A **lot**. Removed a lot of the old functions.
* Replaced `ArnActionGroup` with `SidGroup`. This will allow us to do conditions, etc. It is also easier to read.
* The old `write-policy` logic using `ArnActionGroup` is nuked. Now using `SidGroup`, since that will help us take advantage of condition keys. And it's clean(er).
* `write-policy` is easier to call as a method.
* Unit tests are in a nested folder structure that resembles the rest of the python package.
* Moved to Python Black instead of autopep8
* Replaced a lot of print statements with logging.

Now you can skip the long wait under the `initialize` command - the `initialize` command finishes instantly. To rebuild the database, run `initialize --build`, or to build it with the latest AWS docs, use `initialize --fetch`.