Also, add warning popup when lock is about to expire and allow the user to
attempt to renew the lock. Also, connect the keyup callback for redactor to
the autoLock.handleEvent for greater update of the lock, and also deadband
the lock to every 10 seconds.

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.

Don't add to endTime if not already set

This patch changes the default formatting for text bodies used in emails,
ticket thread, and canned response quoting so that white-space in text
bodies is properly preserved. Previously, the text was treated as raw HTML
and was not properly escaped, nor was the original whitespace preserved.

This allows agents to view the raw email headers parsed with the email when
the ticket or thread entry was created.

Allow for permissions to be registered dynamically. This will
allow for the ability for models and plugins to register permissions.

This resolves #1570

Add ability to add tasks to tickets.

Introduce the initial concept of adding tasks to a ticket.

This will disable the ability for a user to close a ticket when they
have not filled out all of the required fields. Explains the problem to
the user trying to close and directs them to the edit page. Added some
functions to the $ticket class to make it easy to determine the missing
required fields.

This is necessary to avoid confusion vs. closed state.

Redirect to tickets listing page when a ticket is resolved or closed via
status change.

Show different messages and placeholder on ticket(s) deletions

This fixes hits when using the MySQL full text search backend

Furthermore, revamp the __cdata system to better support multiple selection
fields. Drop the `.._id` fields and use a coalesce of the ID value of the
entry value or the entry value itself. For JSON backed fields, strip some
JSON characters to result in a comma-separated list.

The search engine now uses MySQL FIND_IN_SET to analyze a search selection
in advanced searches. Also, interaction with the MySQL full text search
backend is fully supported.

Set the correct error message and maintain user selection & input

Make the error message clear

Fix search backend to use the new statuses

Reserve 'archived' state for automation

Move ticket status change to unified backend.

Merge conflict caused the inclusion of the template to be lost