And extend the information to email templates

Fixes #23

Fixes #77

If a form field is required, then a name will be necessary in order to plumb
up the API.

The quickList() method will attempt to ask the database to find filters that
might match the incoming ticket information. The idea is that MySQL is
likely faster than PHP. The problem is that it assumes positive logic is
being utilized.

This patch adds all filters with at least one rule with dn_contain
(does-not-contain) or not_equal (not-equal)

Add information about current software versions, server software, php
extensions loaded, and database space usage.

In the future, this will offer a nice place to add an import/export button
for data backup and restore, announcements, and more

Fixes #64

Fixes #65

Fixes #78

Fixes #80

If the HTML ticket thread is enabled and the message is not explicitly
declared to be text, then assume it is an HTML message.

Also ensure that the ticket thread is displayed in a <div> container as some
browsers seems to frown upon <iframe>s in <td> elements

Fixes #75

formset_id was not renamed to form_id after our rebase

PHP can't discern the difference between d/m/Y and m/d/Y when just the date
is submitted to strtotime(). Unfortunately, strptime() is not available
until PHP 5.1.0. This patch forces datepickers to change their values to
YYYY-MM-DD upon submission to disambiguate parsing issues.

Fixes #832

This will hopefully remove some of the confusion from the repeated
names in the various initial data

Previously the American date format (m/d/Y) was used exclusively for
formatting dates in the datepicker widget. This patch enables the widget to
be formatted based on the format set in the admin panel.

Fixes #829

If a Content-Disposition header exists for an attachments, it isn't required
to have any parameters (like a file name)

Overhaul the popup tips from the installer to make them translatable and
work toward popovers for all the admin and staff panel settings.

Also remove CSS properties from the style attribute that are browser
specific (like -webkit-* and such)

Previously, clients would not be able to create tickets if an internal,
required field existed on any of the forms presented to the user. Instead,
they would be stuck at permanent validation failure because there was no
data for a required field not shown.

This patch adds a feature to the form and dynamicFormEntry objects'
isValid() method to receive a callable to filter which fields' errors should
be added to the form's errors list. This allows for more complex validation
where in some cases, validation errors should not be considered on some
fields.

Fixes #45

Fixes #40

Move the cacheable code to the Http class and allow the client configuration
to be cached in the browser

Which will help fight off spammers. This should be coupled with logic that
will add some enticing fields, like 'email' and 'name' to invite bot input.
Then, on the form processing side, a spam submission can be detected and
handled differently from human submissions. This should lessen reliance on
CAPTCHA only as spam detection.

Previous the options defined for the Mailer::send() function were confusing
when sending an In-Reply-To header