Also, write js and css links to be forcibly reloaded by the browser after
deployment

When the include path is written in bootstrap.php, ensure that extra slashes
are not accidentally added

Fixes #20

This will allow an administrator to visualize the files changed in the
deployment before actually copying out the new files

Turns out that the $args passed into the run() method of the Unpacker are
not correctly utilized and so, it is not correctly extensible

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

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

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.