Add computed columns to soda fountain upsert flow

- Factored out RowDataTranslator from RowDAO and separated out client JSON -> SoQLValue and SoQLValue -> DC JSON
- Computed columns field name must start with colon, this ensures they are treated like system columns in select statements (returned in SELECT :* but not SELECT *). There were a bunch of ways we could have implemented this but based on talks with Marc, Robert, Franklin this had the best tradeoffs for now.
- Tightened up some of the column validations in Soda Fountain (a) Currently 2 columns are allowed to have the same field_name, which creates ambiguity in SoQL SELECT statements. (b) Don't allow client to specify computed column values in an upsert/replace
I don't think we can reorder the deletes and upserts, even for a smaller batch.   What if the original data stream had this:

Delete(row=15)
Upsert(row=15, .....)

The way this is now implemented, the delete will then get reordered to be after the upsert.