This allows for less work when designing new queues. The column design—the
data definition, annotations, and conditions, are saved with the column. The
heading, sort order, and width are set when the column is associated with a
queue. This means that changing the behavior of a particular column will
mean not having to redo work for each queue that uses the column.

This is a new concept for many-to-many relationships, where the extra fields
from the middle table can be overlaid over the related model using the
AnnotatedModel paradigm. The overlaid fields are writable and updates are
saved to the middle model.

This is performed using a new ::wrap method of the AnnotatedModel class.

AnnotatedModel::wrap($what, $overlay, [$class])

Which will create a new class which is a subclass of `$what`, and will have
the extra properties in `$overlay` accessible as normal properties.
`$overlay` can be an array or a VerySimpleModel instance. The latter is
required for writable overlays.

This adds support for adding "personal" queues underneath any top-level
queue with automatic criteria inheritance.

Attempt to only use parentheses in WHERE clauses and friends when
mixing ANDed and ORed constraints

This retires the "Show assigned tickets on open queue" and "Show answered
tickets on open queue" settings.

And also fixup custom data fields used in conditions

The filter concept will allow for more sophisticated concepts including date
formatting, and will also allow plugin interaction.

And add options for custom data form fields