This addresses an issue where the previous CSV security patch causes an
error when creating an Advanced Search with criteria like `User / Email
Address => contains => @domain.tld`. The system tries to validate the field
and since `is_formula` is the default validation for TextboxFields the
system sees `@domain.tld` criteria as a formula and throws the `Content
cannot start with the following characters: = - + @` error. Advanced
Searches do not need the `is_forumal` validation as the fields are not
exportable. This adds a check to see if the field's form is
`AdvancedSearchForm` and if there is no `validator` set it gets set to `adv`
which bypasses the validation.

Required Short Answer Field = '0'

Date Range Period  / User's Timezone

issue: Department Referral Email

This addresses an issue where a User sending an email message with a
different Department as CC to the system will not refer the CC'ed Department
until the email is fetched a second time. The old thinking was that since
the User CC'ed the other Department the other Department should receive a
copy of the email in their mailbox. When the system fetches the User's
message from the original Department email it gets added to the thread but
doesn't refer just yet. When the system fetches the copy of the message from
the User in the other Department's email it will then refer the other
Department. This is a problem especially when you are not fetching or
forwarding from the other Department's email address. This updates
`Thread::postEmail()` to include the check for `$mailinfo['system_emails']`
and if set we refer the Department immediately.

This commit fixes an issue where date range boundaries didn't consider
user's timezone resulting in UTC times being used.

Issue/ticket preview collabs

i18n: Register Include

This addresses issue 4965 where the register.inc.php file for clients was
missing translations for the action buttons.

issue: Set Staff Password On Creation

Update osTicket Requirements

- PHP 7.0-7.3
- MySQL 5.5

feature: Expanded Print View

issue: Dashboard No Help Topics Error

Update osTicket Requirements

Issue: Undefined Constant Warning

For the is_a function, the class name should be in quotation marks to avoid the warning in PHP 7.3

Recommend PHP 7.3

Conflicts:
	bootstrap.php
	include/ajax.orgs.php
	include/class.dept.php
	include/class.file.php
	include/class.organization.php
	include/class.staff.php
	include/staff/profile.inc.php

Issue: Inline Ticket Assignment

issue: Error On QueueSort Config

Issue: Reopen Assignment

issue: Image Attachment View

issue: Update Installer PHP Requirements

issue: Support Exchange Shared Mailbox Auth

issue: Advanced Search Default Sorting

Fix Admin Alert

issue: Update Outdated Links

Organization Update

This addresses an issue where the system cannot successfully authenticate to
an Exchange server using shared mailbox auth credentials (eg. Username:
`main-user@domain.com\shared-mailbox@domain.com`). The system passes the
entire Username value as the `username` parameter for `imap_open()` and
Exchange fails to authenticate. This adds two new variables called
`authuser` and `username` to class MailFetcher. This also updates the
`MailFetcher::__construct()` method to explode the Username value at the
backslash giving us two parts: the Authentication Username and the Mailbox
Username. If there are in fact two parts we will assign the first part to
the new `authuser` variable and assign the second part to the new `username`
variable. If we detect an `authuser` we will add it to the `imap_open()`
flag called `authuser` and append it to the `srvstr`. In addition this
updates the `MailFetcher::getUsername()` method to return the new `username`
variable instead of the hash table data.

Within a Ticket, if you click the Assign dropdown and choose Agent or Team, the possible assignees are filtered based on who can be assigned to the Department, however, the inline Assigned To option did not filter the possible assignees. This commit ensures that we do filter possible assignees when assigning via inline edit.

This addresses an issue reported on the Forum where visiting the Agent
Dashboard with no Help Topics in the system completely breaks the Dashboard
view and throws a database error `You have an error in your SQL syntax;
check the manual that corresponds to your MySQL server version for the right
syntax to use near ') GROUP BY A1.topic_id' at line 1`. This is due to the
statistics code assuming we will always have `$topics` but this is not
always the case, as some people rock their helpdesk without a single Help
Topic. This adds a check to see if `$topics` is empty and if so, we return
the appropriate headers with an empty array as the plot data. This will
avoid the database error and show the appropriate Dashboard view with no
statistics listed under "Topics" tab.

This commit addresses an issue where updating (editing) organization from
User's page resulted in ALL settings getting cleared. The change makes sure
the update is routed to the proper routine.

This addresses an issue where conducting an Advanced Search will show the
results in ASC order (from oldest to most recent) by default. If there are
no keywords the search is supposed to show the results in DESC order (from
most recent to oldest) by default. If there are keywords the search is
supposed to show the results sorted by `relevance`. This adds additional
`select` options to the search criteria for keyword searches so that we can
use `relevance` in the outer query. This also adds an `order_by` to the
tickets to order them by the `relevance` in `DESC` order. In addition this
adds a new `order_by` to sort the results by `created` in DESC if there are
no keywords.

This updates the Installer PHP Requirements from `5.4` to `5.6`. This
updates the `$prereq` variable to be protected and updates depending methods
so they can use the static variable.