Fix width of the ticket thread body
Add consistent font styling between Redactor and thread body

This include URLs in embedded links as well as URLs for external images and
videos embedded via iframe elements.

Also add images on pages to the drop-down list for image choosing, and fix
display of images on the client portal.

Allows the client to be changed on a ticket. Previously, only the
information about the client associated with the ticket was editable. This
patch permits assigning a completely different user to the ticket.

Previously the richtext editor introduced the loss of the collision
avoidance feature.

  * Upgrade to Redactor 9.1.7
  * Use a (x) icon from font-awesome for the dialog

Since the ticket thread is nested in a div now (required for inline videos
to be displayed correctly), the image hover caused the images to be shown at
the end of the thread entry body rather that its original location.

Before, the draft was only cleaned up when progress on the ticket was
tracked with the reply box.

If a form field is required, then a name will be necessary in order to plumb
up the API.

Add information about current software versions, server software, php
extensions loaded, and database space usage.

In the future, this will offer a nice place to add an import/export button
for data backup and restore, announcements, and more

Fixes #64

Fixes #65

  * Dialogs are scrollable if too big
  * Placement does not respect scroll position now (fixed position)

Fixes #834 (again)

PHP can't discern the difference between d/m/Y and m/d/Y when just the date
is submitted to strtotime(). Unfortunately, strptime() is not available
until PHP 5.1.0. This patch forces datepickers to change their values to
YYYY-MM-DD upon submission to disambiguate parsing issues.

Fixes #832

Previously the American date format (m/d/Y) was used exclusively for
formatting dates in the datepicker widget. This patch enables the widget to
be formatted based on the format set in the admin panel.

Fixes #829

Only clean note drafts unless the ticket is being closed.

This means that drive-by mouse hovers, where the user likely did not intend
for the hover to actually popup the banner with the filename and download
button, do not trigger the popup. This patch changes the popup effect so
that it requires a 500ms hover before the popup is shown.

Including adding support to the TCL uninitialized variable reader to ignore
class-static variable access as well as detect inline functions and their
closure arguments.

Moved to an initial form which specifies the ticket's priority and issue and
changed the rendering to render things properly. Now the user can decide
where priority shows on the client side, and the priority privacy setting is
placed in the dynamic form wizard.

The standard form is added to every ticket without option. Extra forms can
be defined and associated with help topics which can additionally be added
to tickets upon creation. This allows for standardization of the dynamic
data location for searches and filtering.

Implemented advanced search for dynamic data. Along with reinstating the
basic ticket search on keywords

Implemented ticket filtering on dynamic data for both keyword searches as
well as searches for special fields (drop-down lists, etc.)

Phone number for users is now completely optional

This moves client information like name and email address out of the general
dynamic forms data for a ticket. It really paves the way for the first-class
user of the future.

Previously, form sections were grouped into form sets for reusability. This
patch drops the form sets and makes form sections the new "forms".
Eventually a section-header field will be added that technically does not
add any dynamic data to the form, but allows for the same feature as having
a form set with multiple sections.

*This is a major redesign / rework of the osTicket base*

This patch drops the concept of static ticket metadata and allows for an
admin-configurable arbitrary data that is attachable to tickets

The system is architected such that the base osTicket install now comes with
a "default" form that has fields for subject, name, email, and phone number.
This form is editable to allow for the addition of arbitrary other fields;
however, the basic fields must remain in order to be associated with a
help-topic and attached to a ticket.

This concept can be expanded to allow for arbitrary data associated with
registered clients or ticket thread items.

Forms are comprised of sections. Sections have a title and instructions
properties and a list of fields. Fields have various implementations to
represent different data such as text, long answer, phone number, datetime,
yes/no, and selections, and are configurable to define the look and feel and
interpretation of the respective form field.

Dropdown lists are represented as "Dynamic Lists", which are
admin-configurable lists of items. Dropdowns can be optionally represented
as Bootstrap typeahead fields.

This also adds the start of a simple ORM which will hopefully be expanded in
the future to support multiple database platforms. Currently, only MySQL is
implemented.

Process inline attachments in thread entry and support inline images in
piped emails

Support inline images across the system, with draft support

Migrate to a single attachment table
    That way we don't need a new table for everything we need to attach an
    inline image to (like a signature, for instance)

Add richtext support for internal notes

Implement images on site pages

* Image paste in Redactor
* Make non-local images optional
* Placeholder for non-local images
* Fix local image download hover
* Don't re-attach inline images