feature: Manage Referrals Role Permission

feature: Release Role Permission

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.

Code Improvement

Agent Ticket on Behalf of User Fix 2:

This commit addresses a bug where "referral check" filters were not being
considered when checking if a thread is referred to one of the agent's
departments or teams.

Department Ticket Assignment Options

issue: Queue Export Sorting

issue: Choices Field Export

This addresses an issue where the Queue Export does not remember your
column sorting. This was due to the `getExportableFields()` function
called in the Export Template that gets a predefined list of fields plus
some `cdata` fields with a predefined sort order (not your saved sort
order). This updates the export template to merge the `$fields` array that
contains the exportable fields in the saved sorting order and the
`getExportableFields()` result (array) that contains the same fields plus
`cdata` fields. This will return the fields in the saved sorting order
whilst still displaying possible `cdata` fields.

This commit fixes an issue when an Agent creates a Ticket on behalf of a User, includes an Initial Response, AND chooses 'Do Not Send Alert' for the Ticket Notice. In this instance, ONLY the Agent's initial response should be sent to the Ticket's User and Collaborators so that they will know they are included in a Ticket.

In order for this logic to work, a literal check had to be done. If the emailreply variable is set to the string literal 0 (which means do not send alert was selected), say that the alert variable in postReply is true so that the Response/Reply template will go out with only the initial Agent response. Otherwise, if emailreply is 'Alert User' or 'Alert All', the alert variable in postReply will be false and the New Ticekt Notice template will go out, showing both the user initial message and the agent initial response.

This addresses an issue where exporting a ticket with a Custom Choices
Field does not export the Custom Choice data. This is due to the
`ChoiceField::getChoice()` function that doesn’t add the correct `id` to
the `$selection` array. This updates the function to include the `id` in
the array so we can get the correct value later on.

Internal Email Forwarding

Issue: Agent Export Department Status

Issue: Translating Archive Selections

This commit changes the Agent export to display (disabled) beside the name of Departments on the export if they are Archived or Disabled. This will help Agents determine if an Agent is not assigned to any active Departments.

This commit avoids camel casing the select values for Archiving Help Topic and Department options. It also fixes an issue where the selected value was being translated and it should not have been.

Give agents department's ticket / task create, by default, unless explicitly
denied by an assigned role.

Make subjects bold (by default) when ticket is unanswered

Add ticket reopen count as a column annotation

Issue: Dumping Tickets From User View

Agent Ticket on Behalf of User Fix:

Issue: New Task Department Sorting

This commit fixes an issue where Departments were not in alphabetical order when opening a new Task. This will also ensure that Departments will be alphabetically sorted anywhere that contains a DepartmentField.

This commit fixes an issue with how we export tickets from a specific User. Since changes were made to how Ticket exports are done, we needed to modify the call to export the Tickets from users.php as well since we were unintentionally sending the file name in where the csv headers should've been (variable added in dumpTickets method).

This commit fixes an Issue that resulted from allowing Agents to add Collaborators when opening a Ticket on behalf of a User and being able to decide who will receive an email alert. If an Agent were to add an initial response to the Ticket, two email alerts would be sent out (New Ticket Notice and Response/Reply Template). Now, only the New Ticket Notice is sent out unless the Agent chooses not to send any alert.

Additionally, if the Autoresponder is set to NOT alert a User when an Agent creates a ticket on their behalf and the Agent includes an initial Agent response, the Response/Reply Template is sent out.

Addresses issue with agent/assignee sorting

Conflicts:
	include/staff/ticket-view.inc.php

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