Take into consideration the auto-response settings when sending out new
ticket by staff notice to the end user.

The ticket number regex was changed with the advent of custom ticket
numbers, and it matches the closing punctuation in [#12345], that is, the
closing bracket would be included in the ticket number sought in the
database. Therefore, it would never match the ticket number properly.

The new regex attempts to match punctuation and non-punctuation groups so
that punctuation in the middle of the ticket number is matched; however,
punctuation at the end is not. So #12345+DEPT will match properly and will
ignore any trailing whitespace and punctuation.

Previously, this was not ported properly now that multiple selections are
supported in the choice field and derivatives.

There was a slight issue when transitioning from a short answer field to a
drop-down field, and when the CDATA table is dropped and rebuilt.

Prior to osTicket v1.9.4, drop down lists only allowed for a single entry.
After upgrading to 1.9.4 the database data for drop downs changed to allow
for multiple entries. However, the old data format was not properly handled
by the SelectionField::to_php() method which handled interpreting and
upgrading the database data.

Keeping the transaction active for the entire request increases the
likelihood of a deadlock on Galera clusters.

Especially on Galera clusters, search indexing with MyISAM tables will cause
unstable clusters and loss of data. For standalone clusters using MySQL 5.6
or MariaDB 10.0, the database default table storage engine can be used,
since either support fulltext indexing.

Determine and set a reasonable max file size on install
Remove file extension restrictions - transition to mime types

For fields with `name`s which are the same as other fields on the new ticket
form (such as `time` used with the new ticket by staff form), ensure that
data from the fields outside the main ticket form ("Ticket Details") is not
mingled with fields inside the form.

Since this is only a problem for web requests, and specifically new ticket
by staff requests, this patch only applies the field name to data matching
for non-web requests.

Add order by method to ticket status list to return appropriate sort columns
Delegate __get method in CustomListHandler to the parent list

Compare the database `state` field rather than the admin editable status
name.

The real bug was setting the source of the ticket form — not the fallback to
the form entry source.  Falling back breaks edits.

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

Use the cdata field when searching and sorting the ticket listing on the
client side.

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.