This commit stores internal notes if an Agent includes one while creating a Thread Referral.

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.

- unset the sessions form data only in necessary places
- refer to a tasks number instead of id in internal notes
- use indexOf instead of includes in js for IE compatibility

- say created from thread entry instead of created from thread
- make sure that links to thread entry do not open in new window
- make sure if default help topic is selected, message data carries over
  - make sure if issue details are not included for a help topic form, we
    make sure there is a message before trying to get attachments for one
- do not pass in an object to session array. use id and do lookup after instead

When a Task or Ticket is created from a Thread, this code
adds the functionality to create an Internal Note in the
new Ticket or Task as well as the original Ticker or
Task to show the activity that happened.

- On ticket edit, only display inactive help topic warning if the ticket has a help topic
- Inline edit file save fix
- Remove future search/filter criteria for datetime fields that can't be in the future
- Fix calculations for 'next 7 days' and 'next 30 days'. They were selecting dates between now and n days AGO instead of between now and n days in the future

Unify ticket visibility as a routine to make sure it's applied uniformly.

Make sure that the task due date is not beyond ticket's due date.

This commit addresses a few issue in commit 131b366d

* Keep thread action triggers self contained
* Refresh the entire ticket page on successful thread action
* Fix bug where ticket id was hard coded

This adds a Ticket Thread Action for creating a Task. This action will
popup the New Task modal and will pre-fill the body of the New Task with
the body of the Thread Entry from which the action was made from.

Example:
Thread Entry - “I will need to check on the status of your account.”
Click Create Task from that Thread’s Actions
System will show New Task popup with the body as “I will need to check on
the status of your account.”

Add ability to select fields / columns to export for queues, including adhoc
searches.

Add ability to add sticky export fields for queues.

Add ability to edit individual fields without the need to mass-edit all
fields.

Refer ticket to current assignee on reassignment
Refer ticket to current department on transfer

Add the initial concept of thread (tickets & tasks) referral.

* Agent & Team
Referring a ticket to an agent or team - is just like assignment without
actually assigning. If referred agent doesn't have access to the ticket's
department then they'll only have view access.

* Department
This is like assigning a ticket to the entire department. Meaning agents who
have access to the referred to department will now see the ticket - what
they can do with the ticket will depend on the assigned role in that
particular department.

It's important to note the ticket will technically be still the
responsibility of the primary department. Transferring the ticket is the
sure way to relinquishing the responsibility.

* Auto Department Referral via email
This will happen if an email is sent to multiple departments. For example an
email with TO: support &  CC: billing will result in the ticket getting
routed to "support" department and "billing" getting a referral of the same
ticket. This allows both departments to have visibility of the ticket -
which is not possible at the moment.

Refer ticket to current assignee on reassignment
Refer ticket to current department on transfer

Add the initial concept of thread (tickets & tasks) referral.

* Agent & Team
Referring a ticket to an agent or team - is just like assignment without
actually assigning. If referred agent doesn't have access to the ticket's
department then they'll only have view access.

* Department
This is like assigning a ticket to the entire department. Meaning agents who
have access to the referred to department will now see the ticket - what
they can do with the ticket will depend on the assigned role in that
particular department.

It's important to note the ticket will technically be still the
responsibility of the primary department. Transferring the ticket is the
sure way to relinquishing the responsibility.

* Auto Department Referral via email
This will happen if an email is sent to multiple departments. For example an
email with TO: support &  CC: billing will result in the ticket getting
routed to "support" department and "billing" getting a referral of the same
ticket. This allows both departments to have visibility of the ticket -
which is not possible at the moment.

This fixes an issue where the `$ht` variable is not properly initialized by
the ORM. It is assumed to be a valid array in the constructor, and its items
are run through the ::set() method. Therefore, if an empty array is
received, the `$ht` variable will remain null, since nothing is ever set.

This also fixes a misspelled variable in the claim dialog if a ticket is
currently assigned to a team only.

Updated several files to split up phrases like "Your lock has expired. Please try again!" into "Your lock has expiredx" and "Please try again!"

Note: Since I'm not sure if that's all (replacing %s %s with %1$s %2$s) which is necessary to make this work, I'm sorry in advance for a potential "bad commit".

As already written on Crowdin, in German the order is wrong, so my suggestion is to make it possible to change the order by transforming "%s %s" to "%1$s and %2$s".
Format in English: Successfully assigned 4 selected tasks
Needed German: Successfully 4 selected tasks assigned

Fix translation so it makes sense.
Before: "Unable to change status for 2 any of the selected tickets" - sounds wired
After: "Unable to change status of 2 selected tickets" - sounds correct and fits into the rest of the translation scheme ;)

This pass also makes a stride at adding correct punctuation and making error
phrases consistent.

This is my attempt at removing similar texts from the translator work load.
It also makes an attempt at dropping some misspelled words and works toward
standardizing some phrases.

Make tasks actions icon based buttons
Fix task assignment issue

Filter assignees based on selected tickets department setting.

Filter members based on department's assignment restriction when building a
list of assignees.

ClaimForm extends AssignmentForm and hides assignees selection. Claimant is
still given the opportunity to log an optional internal note as to why
they're claiming the ticket in question.