Switch LDLite to using the new server side transform

[brycekbargar]

This switches LDLite to using the new transform. The legacy transform is still available by using a parameter passed to the query method. After making the switch and testing with both the unit tests and against Five Colleges production instance a number of regressions were found and fixed. While testing against the production instance the load_history table proved to be a thorn in my side and the v1 was added in lieu of actually using a migration framework for it.

• The catalog table was never implemented
• The array index column was misnamed
• Booleans weren't created as boolean columns
• The column named "value" used during expansion conflicted with underlying column names
• The columns in the output tables were ordered in a random way
• Fields that started with caps would get an underscore at the front of their column name

Indexing for the new transformation will be implemented in the next PR. In testing, this implementation runs out of memory for large tables with large objects. I've experimented with fixes and there will be a follow up performance PR to address this issue.