This addresses an issue where Users updating their profile will throw an SQL
error in the system logs. This is due to a line of code trying to set a
value for the `dst` column which no longer exists as of `1.10.0`.

This adds a Signal to clean Agent and User sessions upon setting/resetting
their password. If an Agent/User resets their own password and has multiple
sessions open it will log them out of every session except the one they’re
on.

This pass also makes a stride at adding correct punctuation and making error
phrases consistent.

Add ability to disable use of authentication tokens on ticket links

This patch changes the automatic GROUP BY clause for annotations in the ORM
including aggregate queries (like COUNT), by allowing the query to specify
"distinct" fields. If distinct fields are specified, then no other fields
are automatically added to the GROUP BY clause of the compiled query.

This will likely only be supported by MySQL, as other engines and the ANSI
standard require all non-aggregate fields in the SELECT clause to be present
in the GROUP BY clause.

This patch makes the open and closed ticket counts on the client portal
relative to the help topic search. It also hides the counts when doing text
searches so that an extra count query isn't necessary.

This greatly improves the performance collecting user and organization
ticket statistics.

The previous code would erroneously include ticket counts from the user's
organization even if the user did not have access to them.

Also fix clobber of password reset user ID's in config table, and fix
cleanup of client password reset tokens from config table.

This patch adds to the client interface the ability to filter tickets on the
client portal by help topic, as well as a "clear" feature to clear search,
sort, and filter options.

Also, fix the links to the ticket queue search (again)

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.

References:
https://bugs.php.net/bug.php?id=43200
http://stackoverflow.com/a/22521203

This patch suggests a change to the message-id creation process that
includes stamping the receiving user-id (staff or client) along with the
thread-id of the originating notice. This allows detection of threading if
the clinically brain-dead mail client drops all the other header detection
mechanisms, including the tag placed in the email body, on response.

This patch works for both client and agent communication.

References:
https://bugs.php.net/bug.php?id=43200
http://stackoverflow.com/a/22521203

  * Fix missing attachments join for Category (fixes #1654)
  * Fix crash on user account registration
  * Fix save button on user account (fixes #1655) — regression from bebc2d79

Use http::build_query instead of inline urlencode

This patch suggests a change to the message-id creation process that
includes stamping the receiving user-id (staff or client) along with the
thread-id of the originating notice. This allows detection of threading if
the clinically brain-dead mail client drops all the other header detection
mechanisms, including the tag placed in the email body, on response.

This patch works for both client and agent communication.

This will help if the user has "Browser Preference" selected as the
preferred language. When email correspondence needs to be sent to the user,
the browser_lang extra attribute can be used as a backup to to the user's
language preference in the event that the language preference is set to auto
(Browser Preference).

This is necessary to avoid confusion vs. closed state.

Also, fix duplicate emails where a user as a collaborator would be sent a
confirmation for their own respective email.