Session never expires

Reviewed-By: Peter Rotich <peter@osticket.com>

logo: Allow customized SCP logo

Reviewed-By: Peter Rotich <peter@osticket.com>

Fix very predictable random data on some platforms

Reviewed-By: Peter Rotich <peter@osticket.com>

Revert "Disable auto-responses on staff created tickets"

thread: Remove collaborators when removing the thread

Reviewed-By: Peter Rotich <peter@osticket.com>

charset: Normalize charsets

Reviewed-By: Jared Hancock <jared@osticket.com>

This pull request adds a cleanup util for bogus and invalid charsets, mostly
added by a nameless company out of Redmond, WA.

Fix SLA link in help tips

Reviewed-By: Peter Rotich <peter@osticket.com>

This patch sends updated session cookies to the browser when the session is
refreshed on the server. This allows the session cookie to expire on the
browser at the same time the session timeout occurs at the server. In the
event the session timeout is configured in osTicket not to expire, the
cookie will expire after seven days on the client browser, and will expire
in PHP when it is garbage collected sometime after 86400 seconds after the
time last refresh time.

Using this method, the session will never expire if the session timeout in
osTicket is configured to 0, and the session is refreshed at least daily.

Fixes https://github.com/osTicket/osTicket-1.8/issues/1673

Misc::randCode does not generate significantly random data for Windows
platforms with a local database. This stems from the random seed using the
milliseconds from the current time of day and the database connection time,
in microseconds. Because Windows has especially poor sub-second time
resolution via the microtime() function, the seed does not have many
variations.

This patch addresses the issue by using the included Crypto::random()
function as a source of random data rather than the mt_rand() function, as
it uses native cryptographic random data generators if possible to generate
the data, and uses microtime() as a fallback if no other source of random
data is available on the platform.

Tested with 1.9.4 - found no other / related / new issues due to this change of the z-index.

Fixes: https://github.com/osTicket/osTicket-1.8/issues/980
Fixes: https://github.com/osTicket/osTicket-1.8/issues/1411

This fixes a slight issue where the team members would never be included on
the new message alert. Now, the system will send to either the assigned
staff member, if any, or the members of the assigned team, again, if any.

Files upgraded from versions of osTicket prior to 1.9.1 did not have a
`signature` field in the database. For caching purposes in generating the
Etag HTTP header, the getSignature function cascades through the getKey
method. This may be inconsistent in the signed URL creation.

This patch adds a cascade flag to the getSignature method so the cascading
will not happen unless specifically requested.

Don't add to endTime if not already set

forms: Use form's name as the heading.

Reviewed-By: Jared Hancock <jared@osticket.com>

filter: Implement ban on reply-to email address

Reviewed-By: Peter Rotich <peter@osticket.com>

Show the form title on edit instead of "Custom Form" - which can be
misleading since the user might be editing a built-in form.