Emit a backtrace on db_error logs

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

add table prefix to places missing in the query

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

Index form_entry on (object_type, object_id)

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

Address various lint related bugs, typos, and hints

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

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.

Various issues from big feature merges

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

Make initial tickets translatable and HTML

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

    * Ticket created after installation
    * Ticket created after upgrades

Add support for non-standard MySQL port number

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

Add help information about the non-standard port number to the popup tips in
the install screen.

Support MySQL 'localhost' connections using a non-standard port number.
Ordinarily, MySQL will ignore the port setting on *nix systems if the host
is specified as 'localhost'

Dynamic data for osTicket

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

Just add ":port" to the DBHOST during the installation.

Fixup several minor bugs concerning initial experience

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.