This allows detection of some incorrectly-typed email addresses before
tickets, users, and agents are created.

Add ability to extend Form
Support the concept of form ID
Clear/hide field errors on blur

Add ability to import and export list items

This also adjusts the logic internally to lookup the priority by the
priority_urgency field, which should be constrained to follow priority
precedence over the priority_id field.

This patch includes a slight database migration, and adjusts the
functionality of a few core components.

  * Move collaborators from the ticket to the thread.
    This concept allows collaborators on any object which has a thread,
    including tasks.

  * Add flags to the thread entry
    This will allow flagging thread entries for different purposes.
    Initially this can be used to flag the original message of a thread in
    case a ticket / thread is created without an initial message.

  * Lock becomes more of a utility
    The lock is now disconnected from the ticket and is a separate utility.
    Separately, the ticket and task objects can have a reference to a lock
    object. Furthermore, when submitting some activities to tickets, the
    lock is verified to be owned by the respective agent, and the lock code
    must match a current lock code. The code is rotated on each acquire()
    call to guard against double submissions.

  * Collaborator is an ORM model
    The TicketUser class is broken up now so that the collaborator instance
    can exist apart from a ticket. Email message ids are now generated for
    collaborators without respect for a ticket so that collaborators can be
    properly supported on any thread.

This adds the ability to find, activate, lock, and optionally send a
password-reset email to one ore more users in the help desk.

If failing to import file content data, drop contents imported thus far

This patch rebases filters into a row-based layout and redesigns the filter
apply method to be more extensible. It also redesigns the UI to be more
dynamic and to allow for actions to be added without database modification
and actions can also have complex configurations.

Help topics can now specify one or more additional forms to be included on
the help topic and can also specify the sort order of those forms.
Furthermore, individual fields can be disabled per help topic, so that
unnecessary fields can be omitted when necessary, per help topic.

The disabled flag is recorded along side the field data so that the field
will not be accidentally added to the form later automatically. There is no
interface in this commit to enable a field which was disabled by the help
topic when ticket was created.

This patch adds an export+import method to the file command line module. The
file export is agnostic of the file storage backend. It writes the files
with the %file record data to standard-out or to the file given by the -f
option. The file is a considered a stream and can quietly be compressed and
can be read back in as a stream (no seeking is performed in the import
process).

Add role to initial admin's profile
Add default timezone

Support duplicate names in different hierarchy
Save path on add/update
Show full department name on transfer

Introduce the concept of tasks. Tasks are to do list that can be attached to
any object e.g Ticket.

Use generic attachment table for all attachments system-wide.
Drop thread entry attachment table

Detach conversation thread from ticket to make it more generic. Any object
can now have its own thread complete with entry type and attachments.

Use generic attachment table for all attachments system-wide.
Drop thread entry attachment table

Detach conversation thread from ticket to make it more generic. Any object
can now have its own thread complete with entry type and attachments.