DynamicList initial data

Add TicketStatus class and ticket_status table

Change v1.8.2 to v1.9.0
Drop help tips for list properties

Previously we required an account to associate a user to an organization.

This will make upgrades from osTicket < 1.8.0 substantially faster and more
reliable, considering that the previous ticket threads will not need to be
explicitly converted to html.

There was a major goof for osTicket 1.8.0 where the installer created a
`form_id` column in the `%filter` table; however, the upgrader neglected to
add the column. Therefore, users who have upgraded from a version previous
to 1.8.0 will not have the `form_id` column in their database whereas users
who installed osTicket >= v1.8.0 and upgraded will have the column. Since
MySQL has no concept of `ADD IF NOT EXISTS`, this dynamic query will
assist with adding the column if it doesn't exist.

Thanks, http://stackoverflow.com/a/16405301/1025836

Client accounts now that the user is verified either via staff or the
client's email mailbox, there's a much lower risk to showing a verified user
other tickets and virtually no reason that an administrator should have to
turn the feature on.

This is necessary to avoid illegal mix of collations error during upgrade
for MySQL with strict language setting.

Because the file type normally defaults to the system default (for fetched
emails at least), the backend char was not saved, because the file type char
was left at the system default. Therefore, if a file is saved to a backend
other than the default (in the database), the data will likely be saved to
the backend, but the file metadata will reflect the incorrect backend.

The only reason the file type char was not defaulted in the
AttachmentFile::save() method was for the migration process from osTicet 1.6
to osTicket 1.7. This is mitigated by passing `false` specifically from the
migration task.

Since otherwise the file type char is now set, the backend char is now saved
with the file metadata.

They are only available for tickets arriving via the email channel. All
other channel (including email) use the new ticket form to record the
subject and body, which are mapped to the 'Issue Summary' and 'Issue
Details' fields respectively

Structure the drop-down list for the `what` column to be future-minded
concerning custom user data matching.

This patch partially reverts the previous database migration patch which
added a primary key to the table on the `thread_id` column. This column
cannot be used, because there may be multiple entries for thread_id = 0.

This also allows ticket_collaborator.isactive to be negative, as well as
adds the database portion of regex support for ticket filters.

Delete junk records from the %ticket_email_info table before adding a
primary key. Since there was previously no PK, there could be duplicate
records.

Add `attrs` field for backend state information (multi-part migration,
multi-part upload, etc). Change `size` to be an integer rather than text
field. (Storage space will be about the same, but int makes more sense).
Size the `key` and `signature` for ~512 bits. The base64 encoding allows
6-bits per char. At 86 chars, we have 516 bits maximum space.

Fixes the rewriting of the `key` field in the ticket thread body. The
storage de-duplication system may replace the `key` value with an existing
one. The ticket thread system will use the `key` value assigned when the
file is committed to the database or the existing key of the duplicate file.

Also fixup installation issues with the attachment storage plugin
architecture

  * Include a `bk` column to store the storage backend
  * Include a `signature` column which represents a repeatable hash of the
    file contents
  * Rename `hash` to `key` since it isn't a real hash

Conflicts:

	include/upgrader/streams/core.sig

And add fixup rebase conflicts, and add nice page for unconfigurable plugins

There's a unique index on %user_email.address, so there's no need to create
an index on %ticket.email when matching up records.

Fix duplicate phone number (again)

  * Require a label on form fields
  * Require variable name to be unique per form
  * Fixup duplicate phone numbers on upgrade