This begins with a layout manager for forms which will eventually be
designable via the UI for dynamic forms.

orm: Correctly label correlated query joins via sub-queries
orm: Fixup formatting of dates in queries
orm: Fixup mangling of parameter values with colons in sub-queries
misc: Fixup incorrect offset calculation in Misc::dbtime()
forms: search: Add ability to describe a field search
search: Fix crash searching by ticket due date
search: Fix wrong results if searching by a date field (unix epoch was not
    converted to MySQL date format)
search: Fix wrong results searching by date == or !=

Credit: Jared

* Fix crash in Ticket::getLastRespondent
* Fix crash is ORM if using a superclass of a relationship from cache. For
  instance, if the cache contains an ObjectThread instance, but a
  TicketThread instance is required in the relationship. In such a case, use
  the cached data, but change this class. This; however, violates the single
  nature of cache entries.
* Fix spurious events appearing after upgrade due to deleted tickets
* Ensure floating content in thread-body divs does not float past the bottom
* Provide an anchor to thread entries
* Show thread entries before events where both have the same timestamp
* Fix double events for collaborator additions
* Credit email sender with collaborator addition
* Fix incorrect rendering of collaborator addition event
* Fix crash on new ticket due to non-static function
* Fix missing sort on sub-query if explicitly declared in QuerySet
* Fix missing parentheses in SQL for ['field__eq' => QuerySet]
* Fix incorrect SQL on compileSelect for models with inherited $meta['table']
* Dynamically adjust relative time client side

* FAQ Articles
* FAQ Categories
* Access templates

Also log client edits as an event

Few UI tweaks and Team::getLocalName

This patch removes several of the internal notes posted to a ticket for
various events and replaces them with events added to a threads event chain.
The emails are still sent out as they previously were, but internal notes
are only added to the thread if an agent actually specified comments.

This includes adding support to the Redactor editor to force the width of th
editable content to match the width of the displayed content on the client
portal. Also, the landing page displayed on the client portal is themed
(css-class wise) to match that of the Redactor content similar to the FAQ
and thread-entry designer boxes as well.

Instead of selecting the first enabled, visible, non datepicker field, just
use the new @autofucus HTML5 attribute to automatically select the
autofocused field

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

Threads can be edited by marking the original as hidden and setting it's PID to
the id of the new entry. The new entry has cloned data from the original and
sets the `updated` timestamp to reflect the time of last edit. An edited flag
is added to the new entry to reflect its origin.

This patch suggests that agents can edit their own posts, department managers
can edit posts while the ticket is in their department, and that help desk
admins can edit anything.

If a post is edited more than once, only the most recent edit is kept.