Beta release for v0.2.0. This change is meant to coincide with the release of Baseplate 1.0. In terms of "Lines of Code", most of the updates are just running "black" and "reorder-python-imports". We also moved the dev environment from Vagrant + puppet to using docker-compose.
This release has a breaking change it how we configure the underlying `Session` object used by the cqlmapper `Connection`. Rather than setting `session.row_factory` manually, we use a custom `ExecutionProfile` for cqlmapper. This means that it won't work for cases where we were manually setting this like `session.default_consistency_level` and those changes will need to be done in `ExecutionProfile`-s instead. This is the preferred way of doing this come Baseplate 1.0 so it should be done along side that.
There is also another breaking change that goes along with this. Since we are using a custom `ExecutionProfile`, `connection.session.execute` will no longer return a `dict` unless you have configured it to by default, so services that are calling that directly (say to make concurrent requests) will need to account for that. You can do that by either using `execution_profile=EXC_PROFILE_CQLMAPPER` when making the call, configuring your default profile to use `row_factory=dict_factory`, or updating your code to expect namedtuples rather than dicts in those cases.