Migas

This release remove geolocation data collection, ensure fully anonymized data.
Additionally, this includes a shift in versioning, moving away from `versioneer` to `flit-scm`.

A minor version that reworks `status` values, as well as adds `status_desc`, `error`, and `error_desc` to each project.

Hot-fix to prioritize `REDIS_TLS_URL` when establishing redis connection

A hotfix release to ensure projects users tables are properly inserted into.

A patch release to allow server-side control on rate limiting query amount and size

This release incorporates sqlalchemy as the ORM, and adds alembic for migrations.
During this migration, a number of API breaking changes were introduced:

- adds `projects` table to keep tabs on monitored projects.
- defines a new schema (`migas`) to save all tables under.
- adds `is_ci` field (boolean) to `add_project()` resolver and project table.
- adds `unique` support to `get_usage()` resolver.
- removes `MIGAS_DATABASE_URI` environment variable in favor of `DATABASE_URL`.
- adds new environmental variable `MIGAS_DEBUG` to display SQL queries to the console.
- removes `geolocs` location column in favor of `latitude` and `longitude` columns.
- adds `success` field to `get_usage()` resolver.

This release is still compatible with version 0.1.1 of the migas-py client, but some support is limited.
Users should upgrade to version 0.2.0 of the client.