Provide facility to set collaborator status on add.

Fixes a regression in 1.8 where user names and emails submitted via the web
interface would not properly be detected by the filter system for rejection.

References:
http://osticket.com/forum/discussion/75456/v1-8-ticket-filter-for-banning-domain-doesn-t-work

Previously, due to a bug in Ticket::getPhone(), the first digit of the
formatted phone number was displayed only. This patch will allow display of
the entire formatted phone number.

Fixes osTicket/osTicket-1.8#248

'where 1' and 'where 1=1' gives me hives...

If a ticket is currently unassigned and your respond to it, it's yours. If a
ticket is closed and later reopened due to a new message, the last
respondent will always be assigned if available at the time.

Change fromForm routine takes the actual form and do validation and call
fromVars with clean data

Add fromVars to do the actual user creation (previously named fromForm.

Unpack user data for filtering purposes for staff created tickets

Add ability to change ticket owner on ticket view
Add get last updated date to user class

We do not support multiple emails per user at the moment.  We'll revisit the
issue once such support is added.

without required, internal contact field

The detection of inline images in the mail processor causes inline images to
be removed from the attachment list, if listed there. However, the
attachments in the attachment list were not keyed by the attachment-id, so
there was no proper way to detect and remove the attachments from the list.

This patch properly keys the attachment list by the attachment file_id

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.

Fixes a case where multiple tickets are created in one request (such as a
cron job triggering multiple email fetches). The TicketForm::getInstance()
called in Ticket::create() used a singleton pattern to retrieve a cached
instance of the TicketForm. In the case of ticket creation, each ticket
needs a new TicketForm entry instance.

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

Validation errors in user form were not displayed on the interface

Filters should not be run alongside basic ticket validation