Allow staff to cancel user lookup popup when creating a new ticket

Reviewed-By: Jared Hancock <jared@osticket.com>

Make using `realpath` safer

Reviewed-By: Peter Rotich <peter@osticket.com>

The change will allows staff to open a new ticket without going through the
"forced" user lookup popup. On cancel the staff is presented with a
simplified user info form with email and name being the only fields
required.

Revisit template management page

Reviewed-By: Peter Rotich <peter@osticket.com>

forms: Allow decl of prompt and default for choices

Reviewed-By: Peter Rotich <peter@osticket.com>

Ensure a ROOT_PATH is defined for CLI apps

Reviewed-By: Peter Rotich <peter@osticket.com>

Allow the administrator to enter a prompt to be shown in the choices
drop-down for choice fields. Also add the option of selecting a default
value from the list initially rather than displaying a prompt.

filters: Unpack the user information before filter

Reviewed-By: Peter Rotich <peter@osticket.com>

If a user is created / selected before opening a ticket (very likely the
case in the SCP), the email address and name should be unpacked into the
$vars dictionary prior to creating and processing ticket filters

If the entry answer being updated does not affect the ticket details form
(with type=T), then the updates do not need to be applied to the
ticket__cdata table.

Several database performance tweaks

Reviewed-By: Peter Rotich <peter@osticket.com>

This is instead of optimizing the lock table for every cron run, which
wastes a lot of db server io

And deadband session token updates to 1 per 30 seconds

Drop the data table on field type change

Reviewed-By: Peter Rotich <peter@osticket.com>

If a field on the ticket details form changes type, recreate the cdata table

Use config URL instead of THISPAGE

Reviewed-By: Jared Hancock <jared@osticket.com>

THISPAGE is unreliable for CLI cron calls. It was historically used so the
admin could figure out which file/page generated the error. But with
backtrace support we no longer need it.

Arrange templates in a group by their respective use in the system:

  * System Management Templates
  * Staff Ticket Templates (Alerts and Notices)
  * End-User Ticket Templates (Autoresponder)

This provides an interface to sort the templates and make them easier to
find and provides a nice place for new templates to be added without making
it increasingly more difficult to locate templates in the list.

This patch also fixes the missing templates in the drop-down list when
editing an implemented template.

This is necessary because the system depends ticket priority to sort and
display ticket data.

Allow autocomplete on email address

Reviewed-By: Peter Rotich <peter@osticket.com>

Show extra forms for help topic first

Reviewed-By: Peter Rotich <peter@osticket.com>

Fix subject ticket number matcher (again)

Reviewed-By: Peter Rotich <peter@osticket.com>

Use case-insensitive matching on email address

Reviewed-By: Peter Rotich <peter@osticket.com>

This patch addresses an issue where a client may have upper-case letters in
their email address. When visiting the client portal to check the ticket
status, previously, the exact same case would be required in the 'Email
Address' box.

This patch remove the case sensitivity for email logins.

No longer require a priority for help topics

Reviewed-By: Peter Rotich <peter@osticket.com>

Pre-select default priority

Reviewed-By: Peter Rotich <peter@osticket.com>

Extra forms associated with the help topic are now shown above the ticket
details form on both the staff and client interfaces.