line 199: in case of custom upgrade streams, variable $signature contains the last value from the foreach cycle at line 130, not the core schema signature!

line 209: if we do not insert schema signatures for each custom stream, after install osTicket thinks it needs an upgrade and gets stuck (see function isUpgradePending() in class.ticket)

Validate port during installation

Add help information about the non-standard port number to the popup tips in
the install screen.

Support MySQL 'localhost' connections using a non-standard port number.
Ordinarily, MySQL will ignore the port setting on *nix systems if the host
is specified as 'localhost'

Implements/Fixes #769

Support MariaDB version 10.0 and forward, which previously did not appear to
be 'greater than' version 4.4 as in php '10.0' < '4.4'. Performing a split
by the dots allows php to perform a numeric comparison.

Allow the installation to use the same streams config and schema signatures
as the migrater

Allow the install to install mulitple database streams

Allow `streams.cfg` to be implied as 'core', which will default to only
upgrading the core osTicket stream.

Use signature to describe snapshots rather than md5

The installer assumes that the CWD of the running PHP process is setup/,
which isn't necessarily true (if run from a cli module, for instance).

Change the config table from a column-based table to a key-value table
with namespacing. This allows several parts of osTicket to store their
respective configurations in the same table without requiring database
structure updates

'namespace' is reserved in PHP

The installer compares the md5 of the on-disk sql install file with the
signature file shipped alongside. If the signatures do not match, it will
refuse to install osTicket. On Windows(TM) platforms, PHP will automatically
translate newlines to Windows newlines (CRLF), which will corrupt the MD5
hash of the file.

This patch opens the file in binary mode explicitly to prevent the automatic
conversion.

The problem stems from assumed MySQL insert ids. In MySQL clusters, the id
numbers will not necessarily be consecutive. This patch causes the install
and upgrade patches to lookup the assumed values for the linked id numbers.

Make collation consistent - utf8_general_ci.