Commcare-export

This release fixes a major issue with exporting to SQL databases and includes a few new functions and improvements.

**Bugfixes**
170 - fix data not writing until the end of the last batch (introduced in v1.3.0)

This bug may have resulted in data not being written to the SQL database. If an error occurred while writing data to the SQL database any data which had already been read into memory would not be written to the database but the checkpoint would still point to the end of the batch.

**Enhancements**
169 - use `nvarchar` with fixed length in MSSQL to allow indexing
162 - remove whitespace from beginning and end of column names
157 - support for python 3.8

**New features**
167 - add `form_url` and `case_url` Map Via functions
158 - add `format-uuid` function to format UUID hashes

Fixes a bug where you would get an error after exporting 11 batches of data.

Improves data type support

Fixes bug with markdown output format

Increased the default `--batch-size` to `200`. The previous value of `100` was causing the tool to loop forever if more than 100 objects had the same timestamp (a number also used in CommCare HQ).

This release includes two significant changes:

1. The [`--with-organization` flag](https://github.com/dimagi/commcare-export#user-and-location-data) which provides a simple way to export location data and join it with forms and cases.
2. Support for a "Data Type" column in excel query files, which allows you to explicitly set the SQL data type of a column. Columns with explicit data types set will also be created immediately, instead of the first time there is data for that property.

Change the Oracle text column from CLOB to VARCHAR2