Release Versioning - Upgrade docs and new install integration

[schnuerle]

We are working on our first release that changes the database structure.

Currently we are at 2.0.1, and are working on 2.1:
https://github.com/LouisvilleMetro/WazeCCPProcessor/releases

This 2.1 release changes the database by adding fields, filling in data in those fields, enriching the DB, adding a new user, etc. See this branch for details:
https://github.com/LouisvilleMetro/WazeCCPProcessor/tree/schema/refactoring-1

And these issues labelled v2.1:
https://github.com/LouisvilleMetro/WazeCCPProcessor/issues?q=is%3Aissue+is%3Aopen+label%3Av2.1

To accommodate that we are doing two things.

1. Fresh installs - (assigned to Jason S)
   If you are coming and getting the code fresh, then these changes will be handled automatically for you. Terraform will run a Lambda that runs the code here in an initial install file that will be kept up to date:
   https://github.com/LouisvilleMetro/WazeCCPProcessor/blob/schema/refactoring-1/code/sql/initial-install.sql

2. Upgrades - (assigned to Michael S)
   If you are upgrading from one version to another, you will have to manually run DB scripts to make changes. There will be step-by-step directions written for this, and the script will be named and stored like this one:
   https://github.com/LouisvilleMetro/WazeCCPProcessor/blob/schema/refactoring-1/code/sql/update-2.0.1-2.1.sql

We hope to have this release complete before August 8, 2018.