Issue 254

[rhythnic]

What does this PR do?

• Replace Sqlite3 with Prisma and Postgres
• Provide README and Docker helpers for DB migration
• Cleanup repo a bit, update docker-compose file versions to 3.5 to support named networks. Named networks lets us run different docker-compose files at different times and they can all talk to each other by their service names. It comes in handy when running LoRa Server and Prisma.
• Modify travis file. Upgrade docker-compose version in travis to support v3.5 files. Run unit, api, and e2e tests in travis. Remove web-client e2e test from travis. It would have failed due to the changed location of a docker-compose file. Can add back later, but with other 3 tests running, CI is taking a long time as it is.
• Join coverage test command and unit test command. Unit tests generate the coverage file as a side-effect. If CI is successful, the file get's pushed to Codacy.

Do you have any concerns with this PR?

• This is a very large change / involves many changes.
• Codacy is rejecting the commits based on the syntax of code generated by Prisma. We need to relax the standards or limit the scope of what Codacy evaluates in the repo. Prisma generates the code often, so it's not a matter adjusting the syntax once.

How can the reviewer verify this PR?

Make a large pot of coffee and cancel all meetings for the day.

Any background context you want to provide?

Screenshots or logs (if appropriate)

Questions:

• Have you connected this PR to the issue it resolves? #254
• Does the documentation need an update? Included. Docs site update PR coming soon.
• Does this add new dependencies? prisma-dev-client
• Have you added unit or functional tests for this PR? Modified current tests

[dschrimpsher]

The standards in codacy can be changed. https://app.codacy.com/app/cablelabs/lpwanserver/patterns/list