Process inline attachments in thread entry and support inline images in
piped emails

Support inline images across the system, with draft support

Migrate to a single attachment table
    That way we don't need a new table for everything we need to attach an
    inline image to (like a signature, for instance)

Add richtext support for internal notes

Implement images on site pages

* Image paste in Redactor
* Make non-local images optional
* Placeholder for non-local images
* Fix local image download hover
* Don't re-attach inline images

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)

If a user is running off of the develop branch, disambiguate what the
version they are running.

Add stubs.php to include stub classes for built-in PHP classes used
throughout the code. This will allow the testing suite to verify that a
method exists, albeit not in our codebase

Also raise awareness of the hosted platform for osTicket

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

Fixes #667

This is one of the last major hurdles to make osTicket fully translatable.
With the advent of 1.7.0, database migration is based on the MD5 hash of the
install SQL file. Therefore, the install SQL script cannot be modified (ie.
translated) or else the system cannot be migrated, since the MD5 hash will
no longer match up.

This patch pulls initial data out of the install file so that it can be
translatable. Eventually the install worksheet can allow a drop-down box of
the default system language. The default data from that language will be
loaded into the system.

And include the new location of the install SQL script

Drop old mcrypt class

Only use 8 bytes (64-bits) for the IV data (salt) for the encryption keys,
except for Mcrypt, which requires you to query the specific length and use
it specifically.

We should move initial data out of the install SQL file, which will make way
for a few things:

  * Internationalization -- which breaks the migrater model currently.
        Moving the data outside the install script makes it translatable
        without changing the SQL hash
  * Review -- Migrations which add more data don't highlight new features
        that need review to the adminsitrator

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.

This will facilitate a web-based export significantly easier

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

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