When creating traitview and yieldsview, cast the result_type column to
a known type (in a database-agnostic way) so that taking the UNION
succeeds in PostgreSQL.
Added a migration to make a private traits-and-yields view that
includes user information and includes unchecked rows.  The public
traits-and-yields view is now based on this.