This will allow folks following the git development model to checkout the
sourcecode to one folder, follow an upstream git brach, and deploy the
osticket installation from a current branch to a location somewhere.

The deploy process differs from the unpack process in that it does not
assume to be inside an 'upload/' folder from the install zipball, and it
does not deploy the 'setup/' folder.

The include folder is still supported to be installed elsewhere.

- Force destination folder to always have a trailing slash
- Log if verbosity is set to stdout
- Use MD5 to see if copy is necessary

Inside cli modules, use internal stdout and stderr objects rather than
writing directly to the PHP outputs. This will allow for significantly
easier regression testing integration.

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).

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

- 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

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

Since the first department id cannot be assumed

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.

Aggressively package ALL files in include directory - excluding live config file or swap files.

Exclude ost-config.php
Use the correct package name

Add tasks

Use minimized version of css.

Remove piping setting option - it's now part of ticket create service (which include XML & JSON)

Implement remote cron as api task (more to come)

Make collation consistent - utf8_general_ci.

Which will allow for a modular approach to command-line scripting of the
osTicket system. Hopefully, it will alleviate the need to copy+paste code
between scripts and otherwise duplicate functionality between locations. It
will also allow for easier administration of osTicket by shipping scripts to
do things like database maintenance, statistics exports (collectd), data
exports, etc.

The first example script include the capability to unpack the osTicket
installation/upgrade tarball to the destination install path with optionally
placing the include folder in a different location. The script will monkey
patch main.inc.php so that the INCLUDE_DIR define will point to the
installed location of the include/ folder.