This addresses an issue introduced with 4332 where the deploy CLI breaks
upon deploying to an existing location. This checks to see if there is a
bootstrap file in the destination first and if so it uses that one if not
uses the source.

This addresses an issue on the forums where osTicket does not add the proper
values to any custom choices field template variable. This adds an `asVar()`
function to `class ChoiceField` so we can return the proper values for the
template variables.

This addresses an issue where client side column sorting does not work at
all. This is due to the if/else statement that checks for a REQUEST sort
order and if the REQUEST sort order matches an `$orderWays` array value. The
if statement returns TRUE for DESC and sets the sort order to DESC as it
equals '-' (a dash) but ASC equals '' (an empty string) so it returns FALSE
which fails-over to the else statement setting the sort order to DESC. In
addition, this adds sorting icons the the column headers to make it more
obvious they are sortable.

This addresses issue 4339 where the installer footer references the wrong
copyright date.

This addresses an issue introduced with a3d896c8 where TextThreadEntryBodies
are not keeping their new line characters causing the email format to appear
wonky. This balances the entry and then htmlchars it to ensure no XSS.

issue: IE White Screen Of Death

Typo fix, unneeded semicolon

This addresses an issue on the forums where clicking to view the ticket as
an Agent in IE 11 throws a white screen of death. This is due to the
shorthand javascript arrow functions in `include/staff/ticket-view.inc.php`.

 Collaborator Fixes

- Fix for ‘creating default object from empty value’ message
- Add collaborators in the Ticket::create function instead of Ticket::open so that we can getRecipients in postMessage function
- Add relevant thread_entry_recipients in postMessage function for front end tickets (scp or Web Portal)

Note: This in turn fixes Issue #4354

This commit puts the recipient icon (for one recipient or multiple) on Thread Entries created by Users. It also stores email recipients so you can view them in the Thread Entry Actions.

For Emails:
All recipients in the email are tracked

For front end entries:
All recipients who received an alert are tracked

Collaborator Thread Event for Web Portal:

thread: getId On Non-Object

This addresses issue 4347 where opening a ticket without an initial message
for the User and replying to it as an agent, fatally errors. This is because
osTicket does not check if there is a last message before getting the ID
from it. So it tries to lookup the ID of a non-object therefore fatally
erroring out.

This commit makes it so that Users are able to see all Thread Events that pertain to a Collaborator being added to the Ticket.

Email Recipients Revisited Corrections

Collaborator Tickets Visibility:

This commit fixes the counts in the Web Portal based on which Tickets the User has access to.

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

- Clean up/correct notifyCollaborators function
- Make sure function calls are passing in all needed variables
- getContact function added to EmailRecipient class to properly set up email notifications
- Corrections on encoding recipients for thread entries

Ticket-View Collaborator Collapsible Fix:

This commit fixes an issue where the font for the word 'Collaborators' was being overwritten by the font associated with the icon-caret-right class.

Issue: SQL Error Unknown column '__relevance__' in 'order clause'

Update class.forms.php

Update class.list.php

Feature: canned response rendered using select2

Conflicts:
	WHATSNEW.md
	include/class.dept.php
	include/staff/department.inc.php
	include/staff/tickets.inc.php

This addresses an issue that was introduced by a previous attempt to
address the orphaned file query. The previous attempt addressed the
original issue but slowed database performance so this addresses the
performance issue.

This addresses an issue where osTicket did not ensure associated items exist
before saving to the database. This also addresses an issue where the Parent
Topic error was not displayed on page.

It may be possible to steal or manipulate customer session and cookies,
which might be used to impersonate a legitimate user, allowing the hacker to
view or alter user records, and to perform transactions as that user.
Sanitation of hazardous characters was not performed correctly on user
input.

osTicket did not properly sanitize array values in `Format::htmlchars()`.
Some values in the Admin Interface were not properly sanitized and returned
to the response.

This addresses an issue on the Forums where the Auto-Assignment Thread
Event (configurable via Help Topic) uses the Email of the User rather than
the User’s Name. This adds the correct function to retrieve the User’s
Name if the User has an Account.

This addresses an issue where disabling Ticket Locks but setting a time
for the Lock Timeout will always throw a "lock required" error. This adds
a check to see if locks are enabled AND there is a time set. If locks are
disabled it will not throw the error.

This addresses issue 4329 where you can import a User with no email
address via CSV file. Once the User is added and you try to update them
with an email address it fails due to no default email. This updates the
check for email address from `!isset()` to `empty()` which will correctly
check for empty string.

This addresses issue 4322 where deploying via CLI is missing
`bootstrap.php`. This is due to the `get_include_dir()` function that
tries to include a file from the destination which doesn’t exist yet,
causing a fatal error. This updates the function to use `$this->source`
instead of `$this->destination` to correctly find and include
`bootstrap.php`.

This addresses issue 4325 where the Language Pack Locales are mismatched.
The Locale for the first language is displayed on the second language,
etc. This updates the `$manifest` variable to be set before we display
data so the correct `MANIFEST` file is included and all language data is
displayed correctly.