Add ability to disable use of authentication tokens on ticket links

Include collaborated tickets
Pagenate user and org tickets listing
Add ability to export tickets

Hi guys,

had this issue in my mind from before my vacation. Someone over in the forum had the issue that even though he checked "Assigned Agent / Team" the team never got notified. After some research and a closer look I guess Neil found out that he needed to check "Team Lead" and/or "Team members" to enable alerts for the team as well.

So in this case the wording "Assigned Agent / Team" is a bit misleading and I suggest to change it to just "Assigned Agent" or whatever  you prefer ;)

Just made this pull request, so that you don't need to search long and it's (hopefully) easier to understand which "Assigned Agent / Team" is meant since it's there several times at the alert settings page.

Cheers,
Michael

PS: Also I don't know why the first line appears as "removed" and "added" ... didn't change anything here, but anyway, line 126 is the important one ;)

Fixes a bug where a lock icon is shown on tickets listing even when the lock
in question is expired.

Otherwise we might end up with a search term like '"some junk"*' which is
invalid.

Instead of using distinct alone, change to add the relevance of related
items when searching for tickets. In other words, when performing a full
text search for 'xyz', add the relevance of matched user, organization, and
thread objects.

Add a checkbox option within the department setting to disable the "Claim on
Response"

Feature must be enabled globally in order to be disabled locally (duh!)

Load and cache all the attachments on a thread prior to rendering the items.
That removes the need to run a query per thread item to check for- and fetch
attachments.

This feature allows (by option) an organization to allow its members to see
tickets from other members. It can be used beside or instead of the
automated collaboration feature. Now, collaborators retain access to tickets
on which they participate; however, sharing can be used to enable access to
other tickets owned by their organization.

Fixes #2350 in `develop`

This time, use full-text for user and ticket lookup boxes, and drop the
full-table scans from the ticket basic search page. Auto promote searches to
wildcard searches when searching with the user-supplied input yields no
results.

Also, apply requested state to the user and organization tickets search.

If the subject field is something crazy, such as an HTML field, ensure that
the layout of the ticket queue is preserved and properly truncated.
Furthermore, ensure that the HTML is properly rendered on the client and
staff ticket view pages.

Fixes #2410

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