Address issues from the cli framework

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

Include all the modules for `php manage.php --help` invocation. Also, pass
the parsed arguments and options to the Module::run() implementation.

Federate configuration settings

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

- timezone_offset was dropped from the config table at 1.7-dpr1
- upgrader: only apply five patches in one request
- upgrader: fix readPatchInfo to work correctly
- session: support migrating from 1.6 (again)
- config: support migrating from 1.6 (fallback)
- config: no default for 'isonline' setting
- config: fix SQL whitespace issue for schema signature fallbacks
- config: hash 1.6 versions in the schema signature lookup
- upgrader: fix logging bug in attachment migration

Allow (a subset of) the configuration to also be saved in the session to
make session-backed data more consistent and compatible with up-and-coming
multi-site setups.

Attachment settings were merged into ticket settings
SMTPSpoofing feature was moved to per-email rather than global

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

Add mysqli interface to osTicket

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

Add log error param flag

Conflicts:
	setup/inc/class.installer.php

Allow osTicket to install on a database cluster

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

Since the first department id cannot be assumed

Issue/upgrader bugs

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

Update staffmembers.inc.php

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

Update prereq.inc.php

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

Fix incorrect class header info

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

Drop required usage of MyISAM tables, and drop fulltext indexes as they
are not used in the code currently anyway. Also, use a blob to store
session data so as not to waste space with UTF-8 encoding. Lastly, fix
session_id storage to use VARCHAR(255) which is required for versions
of MySQL < 5.0.3, and use ascii for the storage model for the
session_id as it will contain simple characters only.

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.

Add support for SSL certificates in the MySQL connection

'Hightly' should be Highly

Typo

Link to API Docs.