i18n: Consider current locale for CSV delimiter

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

Conflicts:
	include/class.dynamic_forms.php
	include/class.mailer.php
	include/class.organization.php
	include/class.orm.php
	include/class.user.php
	include/client/templates/dynamic-form.tmpl.php
	include/client/view.inc.php
	scp/lists.php

Feature :: Dynamic Forms 1.1 — address major confusion and magic issues

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

This feature addresses a major issue with the initial implementation of the
custom data system. The original system confused the usage of
database-backed field (dynamic-fields) and their corresponding
implementation. This created the need to crate awkward caching pieces to
ensure that validation errors and data was maintained. Furthermore, the
system confused the linking between form instances (dynamic-entry) and the
form used to represent that entry.

This patch addresses the confusion in two ways:

Dynamic form entries do not link directly to the dynamic form. Instead, the
::getForm() method returns something from the forms API directly.
Furthermore, the ::getFields() method does not return dynamic field
instances (database backed / designed fields). Instead, the actual
implementation of the fields from the forms API is retrieved. This allows
the fields to *always* be cached, which helps preserve data and validation
state.

Secondly, the dynamic form uses the same system, so that requests to turn a
dynamic form into a form (via ::getForm) will also result in the same
behavior, again, where the fields are represented as forms API fields rather
than the dynamic fields.

So going forward, the dynamic fields are *only* used to create corresponding
forms API field implementations. The are associated with the dynamic
counterparts as sparingly as possible.

Also fix bug where bogus charset names like `iso` were confused with valid
charset names starting with that text, such as `iso-8859-2`.

When associating objects via the ::set() method or by adding them to an
InstrumentedList, avoid saving the object immediately. Instead, lazily
update the primary and foreign key of the associated objects.

forms: Don't update CDATA when updating old fields

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

Fix several issues with user directory objects

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

mailer: Try harder to find References header

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

filters: Filter user information for email tickets

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

Ensure that the References header that is included with outbound email
definitely includes the References header from an email received into the
system, if at all possible.

When the user is not identified by the web interface, such as processing
email to tickets, attempt to locate and include the user filter information
when matching the filter to the new ticket data.

If an update to an object such as a ticket results in a corresponding update
to the CDATA table, and one or more of the fields have been deleted from the
ticket details form, then, avoid updating the CDATA table for those fields.

This fixes an issue where the CDATA table is dropped and recreated when
fields are added and removed from the form. The table will only contain
fields which are currently on the form when the table is created. Therefore,
deleted fields will never be on the CDATA table and will result in an SQL
error.

Conflicts:
	include/class.thread.php
	include/class.ticket.php
	include/class.user.php
	include/pear/Mail.php
	include/staff/orgs.inc.php
	include/staff/ticket-view.inc.php
	include/staff/users.inc.php
	scp/js/scp.js
	setup/test/tests/stubs.php

thread: Avoid crash with multiple Message-ID headers

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

Unassign on transfer

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

email: Add warning for archive folder for POP

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

This patch adds an error to the page if unable to configure the archive
folder and POP was selected as the mailbox protocol. Generally, POP servers
do not support anything but the INBOX