Add the current backend to the list results output
Add a --limit switch to support limit results sent to a command like
`migrate`

Allows for backend listing, file listing, single file dump and file
migration.

Allow arguments to have sub-command 'options', so an argument like 'action'
can have a specified list of values, each with respective help output.

And install initial data in target language. Also configure help tip
popovers to be in the configured, default system language.

This includes the initial concept of pluggable authentication along with the
initial concept for a plugin management system.

And freshen up the upgrading guide

Also, if any non-shipped .htaccess files exist, don't clean those either

Fixes #60

Allows the deploy script to remove files in the target that are not preset
in the current repository. This patch assumes pure stock osTicket
deployments -or- that the files deployed in the target are also present in
the local repository.

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

Use a PHP setup which uses the built-in PHP tokenizer to parse and traverse
PHP scripts to determine (possible) access to uninitialized variables

Fixes #20

Also, run the tests in the packager. The packager will automatically run the
regression test suite prior to packaging a release. The package will not
build if there is at least one fail from the regression tests.

Useful for initial installs, where deployment of the `setup/` folder is
required for the initial install. Thereafter, deployment can be run without
the setup option so that the rest of the codebase can be maintained (already
supported)

 * web.config
 * pages/{.htaccess,index.php}

Fixes #667

And include the new location of the install SQL script

This will facilitate a web-based export significantly easier

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

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.