Pop up message hyperlink incorrect with changes made by implementing osTicket docs

This adds a setting in the Ticket Settings to give the option of showing the
ticket counts on Top-Level queues. If enabled, this will populate the ticket
counts next to the Top-Level queue names like they used to be. The only
caveat is the counts are triggered by mousing-over any of the queue names as
we only load the counts when we need to display the sub-queues (for better
performance).

This also adds a new format function called `number` (Phase 1). As of now it
will format any integer to a comma separated number (eg. `1337 -> 1,337`).

This commit addresses where wrong "primary" field was used to indicate
Ticket Status column. It also fixes an issue where sorting was done via `id`
instead of `name`.

This addresses an issue where poor little `sort_id` was sadly forgotten for
the two main-level queues "Open" and "My Tickets".

The commit fixes queues display and sorting.

This commit makes Primary Queues buckets for sub queues with forced inheritance of
criteria. Primary queues are now hidden unless there are no sub queues
attached. Agents can still get to primary queue by clicking on it.

The commit also adds default sub queues for Closed queue, utilizing DateTime
periods.

This commit makes Primary Queues buckets for sub queues with forced inheritance of
criteria. Primary queues are now hidden unless there are no sub queues
attached. Agents can still get to primary queue by clicking on it.

The commit also adds default sub queues for Closed queue, utilizing DateTime
periods.

- add event.yaml file
- create the event table using yaml file
- modify installation files to remove state and add event_id

This commit adds an Admin setting that requires a Ticket to have a Help Topic before it can be closed. It can be set by going to:

Admin Panel | Settings | Tickets | Require Help Topic to Close

If enabled, Tickets will have a warning banner across the bottom of the page, a warning banner when trying to change the Ticket status to Closed, and a warning flag beside the field when editing the Ticket.

By default, this setting is NOT enabled.

This feature gives Agents the capability deciding whether or not Users should be able to see Tickets to which they are Collaborators for in their Ticket queues.

By default, Users are able to see all Tickets they take part in whether they are the User for the Ticket or a Collaborator.

If the Agent would like to disable Users seeing their Collaborator Tickets, they can configure the setting here:
Admin Panel | Tickets | Settings | Collaborator Tickets Visibility

- Separate 'message' and 'response' variables on New Ticket Notice so they can be styles separately
- Add Thread Event state for 'released'
- Add 'refer' and 'release' permissions to the Role table
- Update install-mysql
- Update patch file name
- Update core.sig
- Set flags in correct place for class.depts.php
- Make sure when opening Ticket, User stays selected if submitted with errors
- Make sure Mail Box Protocol saves correctly when configuring emails

This feature adds a new Role permission called Release. This permission
(if Enabled) allows an Agent to release ticket assignment. This permission
is configurable for each and every Role in the helpdesk. This also keeps
current functionality where Department Managers do not need the Role
Permission in order to release tickets. In addition to the permission,
this feature adds a new Release modal giving the option to choose who to
release assignment from (Agent/Team/Both). This also adds a comment box to
the release modal to optionally enter a reason for releasing assignment.
Lastly, this adds a Release Thread Event so an event is logged showing who
released who’s assignment.

This feature adds a new Role permission called Manage Referrals. This
permission allows Agents to Manage Ticket Referrals. This permission
is configurable for each and every Role in the helpdesk.

This means Agents can no longer choose to add a BCC User while creating or responding to a Ticket.

This also means that if a User emails in a Ticket where someone is BCC'd, the Ticket will be created without the BCC'd User(s).

If an email is sent where the Department email is BCC'd, a Ticket is created for that Department and other Users in the email are added as Collaborators.

This also changes the response options for Agents. They now have the options to:
- Reply All (User + Collaborators)
- Reply to User (only the User)
- Do not Email Reply

(Previously the options were Reply All, Reply to User, Reply to CC + User, Reply to BCC, Do not Email Reply)

New Ticket UI:
- Clean up recipient section (adding user and collaborators)
- Give agents the option of who to send the new ticket alert to:
	- Alert to All
	- Alert to User
	- Alert to CC + User
	- Alert to BCC
	- Do not send an Alert
- Added option of adding new Users for cc/bcc section using the 'Add New' button

Post Reply UI:
- Instead of having to type to get the option of adding a new user in the cc/bcc boxes, put an Add New button
- Clean up Add New routine
	- Now when adding a new collaborator using the Add New button, the User's name will appear in the cc or bcc box as specified and the Agent can go ahead and write their reply rather than pulling up the manage collaborators popup and forcing the agent to have to save the collaborator changes before being able to type a reply
- Change the option "Reply to Collaborators" to "Reply to CC + User" to avoid confusion

- Change To dropdown to have different reply types
	- Reply to All
	- Reply to User
	- Reply to Collaborators
	- Reply to BCC
- Add a help tip for the new reply types
- Set the reply type selected based on the last user respondent
	- Reply to Collaborator by default or if the last message is from the ticket user or a CC collaborator
	- Reply to BCC if the last message is from a BCC user
- Put User, CC, and Bcc fields below and indented as appropriate (User field is readonly)
- Add a new flag to Agent responses to show which reply type they selected. Put the flag on Agent thread entries

Commit 3944b51d added ability to archive help topics and departments but
failed to port changes default data (yaml files) loaded on install.

This commits adds the correct bits to flags field for both help topics and
departments. It also removes retired 'isactive' field for help topics.

This commits adds ability for agents to configure public queues.

* Customize Columns
* Set default sort & quick filter
* Add supplemental filters (criteria)

To support above features this commit also addresses confusing Advanced
Search UI to make it intuitive when dealing with a Saved Queue vs. Saved
Search vs. Adhoc Search

Updated to fix typo "information" on line 36

This addresses an issue mentioned on the forums where the Helpdesk Status
setting’s Help Tip is wrong. It states that if the system is in Offline
mode then Agents can still interact with the system when in reality only
Admins can interact with the system. This updates the Help Tip to inform
the Agent that only Admins will be able to access the system.

- %queue_sorts needs to exist before queues are inserted
- old queue id numbers need to be moved up to make room for initial queues

This patch implements Nathan's mockups for adding sorting options to the
custom queues. The sort drop-down feature was added for v1.10. This patch
adds the complex sort dropdown back into the custom queue feature, but also
makes the sorting options customizable.

* Add relative and full formats to the filter list
* All dates in queue are database-relative
* Fix very odd rendering of conditions in queue table
* Fix "clip" truncate mode
* Re-implement background color for Priority column
* Allocate no space for hidden annotations
* Add checkboxes to queue preview for closer resemblance to ticket queue
* Add default formats to initial date columns

And, fix bad width on new open queue
And, fix bad criteria on install

This allows for less work when designing new queues. The column design—the
data definition, annotations, and conditions, are saved with the column. The
heading, sort order, and width are set when the column is associated with a
queue. This means that changing the behavior of a particular column will
mean not having to redo work for each queue that uses the column.

This addresses issue 3935 where Configure Alerts & Notices link in
Department settings is outdated. This adds the updated/correct link to
configure Alerts & Notices.

Make sure you cannot reopen tickets with archived Help Topics. Change radio buttons to Dropdown for status.