Support edit/update of dynamic data

This will allow for self filtering form based on options
Delegate form validation to Form instead of DynamicFormEntry

* Preserve external storage flag on field configuration
* User gridlayout to render task's forms
* Use new roles for task's nav

Credit: Jared Hancock <jared@osticket.com>

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

Reset permissions and change primary department and role

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

Allow fields without data to do house-cleaning on deletion.

Support ability to include attachments to FreeTextField.

* Fix search on boolean field

* Fix crash visiting tasks page while ticket adv search
* Fix search on custom fields
* Add search on ticket source
* Move more advanced fields to drop-down

* Log events for AJAX collaborator list edits
* Avoid extra selects for inline image handling
* Avoid using htmLawed to add target="_blank" and class="no-pjax" to links
  in the ticket thread
* Cache instances of IntlDateFormatter; seems expensive to set up
* Cache filetypes Yaml in APC if available
* Cache I18n::getDefaltLanguage() in the request
* Avoid extraneous usage of Model::_inspect and Model::$meta
* Add aggregated query support to the ORM
* Lazily compile SQL query for InstrumentedLists
* Apply `select_related` setting when setting up InstrumentedList instances
* Slight optimization in SqlCompiler::getField
* Avoid double compiling Sql annotations in the ORDER BY clause
* Cache Thread::getEntries
* Break out event types for ThreadEvent for more legible code
* Eliminate one query from Ticket::loadDynamicData
* Fix ticket number bolding if already answered
* Use dependent subqueries for ticket statistics in the queue page, which is
  significantly faster for large data sets (like hundreds of attachments or
  thread entries)
* Fixup sidebar layout on client knowledge base pages

This patch (which needs further development), introduces an extra field to
the %attachment table to store a file's name, in the event that two files
with the same content are stored in the database with differing names. In
such a case, the name is stored in the %attachment table. This allows the
attachment to specify a different name each time the same file is attached
to something in the system.

These fields have been consolidated into the `flags` column.

* Fix attachments not sticking on new dynamic form entry
* Fix attachments not sticking on thread post validation error
* Fix missing inline images in FAQ article viewing
* Fix missing inline images in FAQ article printing
* Fix crash rendering sidebar in staff faq view with attachments
* Rewrite GenericAttachments to be an ORM object
* Port CannedResponse to ORM
* Fix attachments not being displayed when editing a FAQ article
* Fix squirly empty blue box on faq articles with no attachments

The setting is no longer ticket thread specific. Disabling html is now
system wide setting for disable-able textarea widgets as well as email
correspondence.

Also, fix roundtrip encryption if the form name changes (which is based on a
user's session), and avoid saving a NULL value if the password is not
changed when a form is updated.

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.

Chosen has a problem being rendered in a dialog box with overflow:scroll,
because the content of the dropdown widget is truncated with the scrollable
content of the dialog. Select2 addresses the issue by placing the dropdown
box in the <body> and absolutely positioning it into place.

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