Move ticket status change to unified backend.

Ticket numbers are now configurable as a system-default and by help topic.
Previously, an administrator could select between six-digit random and
sequential numbers. Now, the sequence is selectable so multiple sequences
as needed, and a format can be specified to define how the ticket numbers
look. Formats can also be defined for each help topic.

pjax:complete is only called after an AJAX page load. If a user navigates
forward or backward and the page loads from local cache, then pjax:complete
is not fired. pjax:end, however, is always fired.

Add original and last message quotes to canned responses

The default mode going forward will be to insert when Rich Text support is
enabled and append otherwise. To clear the draft the user can simply click
reset or delete draft icon on the bar.

Enable delete draft option on reply & internal note boxes for consistency.

If the advanced search dialog is up, avoid refreshing the page

htmLawed stripped/discarded <div> tags nested inside inline tags such as
<a>. The previous replacement engine would replace <img> tags with <div>
tags and would cause the HTML to be corrupted by htmLawed.

This patch uses <span> tags which have CSS rules to be displayed as
inline-blocks. This should stay truer to the normal sizing and placement of
the original <img> tag.

This reverts commit b6b2b857.

If an agent submits a page via a POST (like updating settings in the admin
panel or creating a ticket) and navigates away via PJAX, if the browser
refresh button were clicked sometime later, the browser would prompt the
user to resubmit the POST data.

This patch avoids the issue by setting the browser's current URL to itself,
which magically clears the POST data.

The proper fix for the issue would be with
[Post/Redirect/Get](http://en.wikipedia.org/wiki/Post/Redirect/Get) method,
which would redirect the browser to a page it could GET after a successful
POST. Therefore a subsequent GET would reload the GET request, not the POST.
However, that would be too much of an edit for now.

References:
http://stackoverflow.com/a/6077822/1025836
http://en.wikipedia.org/wiki/Post/Redirect/Get

If a new PJAX request is started before the current PJAX request finishes,
leave the user interface in a consistent state.

  * Finish and re-start the loadingbar animation
  * Ensure the overlay is hidden
  * Cancel all current animations (without using clearTimeout)

This also fixes other nuances such as the help tips not working after the
PJAX ui state was corrupted.

Make the organization page happy!