Basic build/postgres infrastructure for sqltyped

There should be a better solution both for entering types directly into the
jdbc URL in two places, and also for the dev loading problem (issue #1244 on
play) currently being worked around by packaging a subproject.
Notes on schema and remove redundant account.created
Switch to anorm: proof of concept

Vestiges of slick and sqltyped remain.

Anorm is minimal, a little messy, but fairly straight-forward.

Slick is cute, a nice idea, but messy, messy, inflexible, generates inefficient
queries, requires a lot of boilerplate (e.g., this change removed net 150 lines).

sqltyped is great, but maybe not ready for prime-time, SQL parsing is very
mysql-centric, and pehaps unnecessary.

Ideally I would like a cross between anorm and sqltyped that does jdbc-only
inference at runtime to produce an anorm-like interface.  I have some thoughts
on how this would work, but should move forward on the real work first.  The
main problem is all the dynamic SQL I ended up using.  May be able to be
cleaned up or hacked (sqltyped has something in progress to do this).

duck macros are so much better.