Also fix a crash when re-rendering the new ticket by staff page after a
validation error.

Fixes https://github.com/osTicket/osTicket-1.8/issues/1277 and https://github.com/osTicket/osTicket-1.8/issues/1373

This patch fixes a small glitch where validation might be bypassed for
fields for agents. Previously there was a glitch where required fields would
have their validation errors ignored.

Since users can already log in via their email address, offer a friendly
error message when agents configure the user name to be an email address.

Footer should not be in #pjax_container, because the footer is not rendered
for non PJAX requests.

When processing the value of a DynamicFormEntryAnswer, if there is no
database-backed, value, then use the value of the associated field.

Auto-detect inline attachments
Attached keepers to canned reply

This patch also makes a slight edit to mPDF to allow better detection of
substitions in characters, as the DejaVu fonts shipped do not support Thai
glyphs.

This allows administrators to select a default value for selection fields
deriving from Custom Lists. This has been implemented on the ChoiceField,
but was forgotten on the SelectionField

This addresses cases where incoming emails doesn't include charset and
mailbox may include non-ascii characters.

  * Use the title of "Information" with internal tag of "info"
  * Add "Visibility" column to UI and retire "Required" and "Internal"
    columns
  * Add visibility selection to new fields and show visibility to the user
    information fields when displayed on the ticket details form
  * Make the visibility settings translatable
  * Use constants internally for visibility configuration detection
  * Use a larger input when managing the information HTML content
  * Fix validation errors for new fields
    * Enforce new field name uniqueness
    * Enforce new field name character validation

Under certain intermittent circumstances (usually a significant number of
ORM queries), the ORM will trigger a MySQL error:

Commands out of sync; you can't run this command now

Usually this MySQL error is related to buffered versus unbuffered queries.
However, the ORM already uses buffered queries (MySQL calls it
"store_result"). In this case, it appears there is some sort of race between
fetching the result metadata before configuring the statement for buffering.
(By "race" I mean that the error is not reliably triggered).

This patch seems to fix the issue by configuring buffering before fetching
result metadata — necessary to configure the fetching (output) phase of the
statement.

This is similar to the section break but doesn't have the <hr> element
before it and allows for HTML input (including images)

Improve info display & formatting
Only show 8 chars of the last commit

Add ticket status properties field before loading init data.

Hide multi selection option for typeahead selections

Consider current status settings to determine if a ticket is reopen-able
Show a warning on staff's ticket view if the ticket is not reopen-able