Adjusted all tables to use % instead of px.

Styled dashboard page.

FAQ tweaks: fixed buttons, adjusted layout for all pages concerning FAQ, resolved Consistency issues.

Add ticket count to page bottom. Team-assigned tickets show up in "My
Tickets"

This patch drops the content after the last boundary in a multi-part message
which prevents it from being considered in some case where the available
content sections are not favorable.

Backport me to v1.9

Only send one autoresponse to the same user for new messages sent in a five
minute window per thread. This will stop looping because of bounces and OoO
notifications not flagged as autoreplies

Previously, the Ticket::getLastRespondent() method would find an agent,
seemingly at random. This was aggravated by a logic mismatch in the
Ticket::onMessage() method which would send a message to the last respondent
if the "Assigned Agent" were select in the configuration for the new message
alert.

No. Seriously. Like from 11k seconds down to 0.3 for a full-text search on
several thousand tickets.

This patch makes the open and closed ticket counts on the client portal
relative to the help topic search. It also hides the counts when doing text
searches so that an extra count query isn't necessary.

So, fields with only the 'required' flag set for users are shown for the
registration page.

This greatly improves the performance collecting user and organization
ticket statistics.

The previous code would erroneously include ticket counts from the user's
organization even if the user did not have access to them.

Use `if not exists` in the create statement for the %cdata table so that, in
some race conditions, a MySQL slave would not be crashed because of an
already-existing table.

The previous code resulted in rebuilding the %thread_entry table several
times during the upgrade process. For systems will several hundred or
thousand megabytes of content in their system, this could result in a very
slow or crashed system.

This patch avoids multiple rebuilds of the table by simply creating a new
one and copying the correct values into the new table. It also avoids
possible duplicates when changing collaborators to the new thread system
considering that collaborators were not properly removed with tickets in
previous versions.

The previous logic required the Ticket::PERM_ASSIGN permission in order to
open a ticket. This logic requires that perm only if attempting to assign
the ticket on open.