This patch fixes an issue where a fatal error would be triggered if the
current value of a selection field on a custom form was a custom list item
that has since been deleted.

This patch fixes a glitch in the dynamic forms processing system preventing
the validation and capture of data for help topic custom fields. Now the
`$vars` managed inside of `Ticket::create` is connected directly to the
`DynamicFormEntry` created for the data rather than using the magical
connection to `$_POST`.

Several places in the code initialize a list of objects from the database
and only fetch one item. In certain instances (which seem almost like a race
condition), MySQL will feel like there are more records available in the
database and will complain with "Commands out of sync, you can't run the
command now".

This patch addresses the issue by utilizing the ::one() method of the
QuerySet where only one record is expected. The ::one() method is further
designed to fetch all one results (which satisfies the MySQL client library)
and return the first item.

That patch introduced a bug where the list of dynamic fields for a form is
always empty

New ticket by staff would cause the %{company.name} variable to be
incorrectly replaced as the user's name in email templates.

Otherwise, no column will be added to the %ticket__cdata table and the
ticket queue pages will be crashed (empty).

Allow developers to specify a sorting position for groups of fields
selectable in the criteria select drop-down

This is necessary to allow for other form types to use dynamic data
view/export

Don't save 'name' as dynamic data for organization form.

Add organization class

Otherwise, it might be possible for a forwarded email to accidentally
contain a ticket link, with which a sinister individual might be able to use
to register for account on behalf of the original client, and, at the same
time, be able to change the user's email address to his/her own.

This mostly helps when fields change types. If the type of the field
currently cannot convert previous data to a string (like if a short-answer
field was changed to choices), the textual representation of the PHP value
of the field data is given.

Priority field and custom list fields have a prompt value (shows up only for
drop-down widget). And the short and long answer fields have a placeholder
configuration item.