Fixes #2433

The system would encode 'access -related' as 'access+-related' when changing
the sorting preference and would crash the query. This patch fixes the
search engine code to avoid a BOOLEAN MODE search when improper operators
are used in the query terms, and it fixes the sorting preference system to
properly decode the '+' to a space when rewriting the URL.

Drop the 25 rule limit

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.