Add types translator method to get VARCHAR types.
Use new translator method in REST and external data services.
For aggregates without an operator (COUNT), the result type is a good type for the placeholder argument.
No one needs this method, so don't bother figuring out how to do its test.
Remove collation from all string-like values.
Use the new Z-order type.
Use types translator for more of compilation process.
Use the types translator to answer JDBC meta-data questions.
Use the types translator to populate emulated query column types.
Add types translator methods for "hard" types like date/times.
Use new routines in encoding / decoding PG values, too.
Include nanos for future.
Need to be more careful about what is passed to fromObject.
merge MMcM: More types translator

Merge pull request #1110 from MMcM/sql-layer/more-types-translator
https://github.com/FoundationDB/sql-layer/pull/1110
Update tests to not look for .t3expected files. Rename existing ones.
merge MMcM: Update tests to not look for .t3expected files. Rename existing ones.

Merge pull request #1111 from MMcM/sql-layer/rename-t3expected
https://github.com/FoundationDB/sql-layer/pull/1111
Change collation flag on BLOB types to false, so that they aren't identical with TEXT types.
There is no meaningful distinction between types and expressions at the serice level; collapse those packages.
Add a types registry to the types registry service (!)
Now that types registry is a service, it needs to be wired all over the place, particularly in unit tests.