Nerium

This bugfix release pins `sqla-raw` to > 1.5.1 to avoid incompatibilities with SQLAlchemy 2.x API changes

As of this release, results endpoints with `/csv` format uses `db.stream_result_by_name()` to connect to database for more efficient memory usage. Without streaming, queries returning large result sets require large amounts of memory to both hold the entire result set and perform format conversion. Streaming handles rows and writes them out in batches. Again, only supported for CSV output at this time, as applying Marshmallow formats to JSON outputs while streaming is a harder problem. It's probably a good idea to avoid JSON output for reports expected to return large numbers of rows.

This is a pretty big and exciting release!

- If API_KEY is set in environment, Nerium will check all requests for an `X-API-Key` header, and forbid access to all endpoints if the header value is missing or doesn't match
- Adds support for reading SQL files from an S3 bucket instead of local filesystem
- Moves discovery/documentation endpoints from `reports/` to `/docs`
- As `/docs` endpoints are backwards compatible with v1 API, drops all the v2 endpoints

As usual, see the README for details on usage of these new features!

- Upgraded most library dependencies to latest versions
- Kept Flask and Werkzeug pinned to previous highest working versions (later ones are breaking tests and will have to investigate/fix before upgrading)
- Bumped version number for PyPi

- Use raw.db.result_by_name for query submission
- Parse metadata based on YAML delimiters instead of meta
- Submit entire file as statement instead of splitting out comments first
- Remove pipenv in favor of pip-compile
- Fix missing json args bug in csv result endpoint

Query namedtuple object was using a `defaults` option introduced in Python 3.7. This release supports earlier python3 versions