This addresses issue 5084 by partially reverting commit `fefed147`. In said
commit, we updated `THIS_VERSION` to utilize `MAJOR_VERSION` which is fine.
However, we also updated the deploy module to copy the same format. This
interferes with the osTicket Version check by not including the entire
subversion and not starting with a `v` (ie. `v1.12.3`). This reverts the
copied format section of the commit so that `THIS_VERSION` will be the full,
non-git version when deployed/packaged.

This addresses an issue where using osTicket from git would show the
incorrect git version in `Admin Panel > Dashboard > Information`. This is
due to a hardcoded git version of `1.8-git`. This updates `THIS_VERSION` to
utilize `MAJOR_VERSION` so that it sets the correct git version. This also
updates the `deploy` CLI module to match the same format (example:
`1.12-git`).

This updates the variable name that determines if the current PHP version is
5.6+ from `$php56` to `$php56plus`. This will help other understand better
what the variable is/does.

This addresses an issue where the `package` cli module is leaving out the
permissions on files. This causes the final ZIP archive to contain files
without permissions meaning the files are un-usable until you restore
permissions. This can make life difficult on people trying to install
osTicket with minimal knowledge as they wouldn’t know what is wrong.

This is due to the `setExternalAttributesName` method not shifting 16 bits
on the file "mode" which will not translate to binary. The file "mode" is
the inode protection mode for a file returned by the `stat()` method. It is
essentially a decimal representation of a file's permissions. Since "mode"
is in decimal format we need to shift by 16 bits to translate it to binary
so the archiver understands. Once the mode is translated to binary the
permissions are preserved.

This fixes PHP issues compiling language packs with PHP after version 7.

This patch fixes the issue where the configuration was not properly
reloaded during an upgrade. The configuration items were stashed in the
Config class and were not re-fetched from the ::load() method.
Additionally, this patch forces the ORM cached objects to be flushed on
each loop through the automated upgrader to ensure that cached data
which might have been modified directly in the database during the
database process is destroyed.

This addresses an issue introduced with 4332 where the deploy CLI breaks
upon deploying to an existing location. This checks to see if there is a
bootstrap file in the destination first and if so it uses that one if not
uses the source.

This addresses an issue introduced with 4332 where the deploy CLI breaks
upon deploying to an existing location. This checks to see if there is a
bootstrap file in the destination first and if so it uses that one if not
uses the source.

This addresses issue 4322 where deploying via CLI is missing
`bootstrap.php`. This is due to the `get_include_dir()` function that
tries to include a file from the destination which doesn’t exist yet,
causing a fatal error. This updates the function to use `$this->source`
instead of `$this->destination` to correctly find and include
`bootstrap.php`.

This addresses issue 4322 where deploying via CLI is missing
`bootstrap.php`. This is due to the `get_include_dir()` function that
tries to include a file from the destination which doesn’t exist yet,
causing a fatal error. This updates the function to use `$this->source`
instead of `$this->destination` to correctly find and include
`bootstrap.php`.

Crowdin requires a `branch` argument when requesting the language pack
download from their system.

With the advent of the MANIFEST file, files which are rewritten when
deployed, such as those which have the GIT hash in the query string to force
browser reloading, were no longer deployed unless the content of those files
changed.

This patch adds a flag to the MANIFEST file to indicate that the file was
rewritten when it was deployed. This allows the file to be deployed and
rewritten again when the deployment is run, but also adds an indication
to the console output to distinguish deploying changes as opposed to
deploying rewrites.

Also, add build version and path information for the PHAR files listed as
language packs.

Since two major versions will internationalization support will soon be
available, the language pack system will need a way to indicate which major
version of osTicket the phrases were compiled for. This patch adds a
`Phrases-Version` tag to the MANIFEST, which will be a copy of the
MAJOR_VERSION included in the messages.pot file created via `make-pot`.
Then, a `Build-Major-Version` tag is added to the MANIFEST which represents
the version of osTicket used to compile the language pack.

Ordinarily, both strings should be the same, and they should also both match
the MAJOR_VERSION of osTicket when the language packs are loaded on a
production system.

This also adds support for PHAR compression in the build process. Since
accessing a PHAR file in a request burns 1ms per megabyte of PHAR file,
reducing the PHAR file size by up to 77% means that much less time spent
loading PHAR files. This can be especially useful for a busy server with
support for several languages. But, ZLIB or BZIP2 support would be required
for all production servers.

This is my attempt at removing similar texts from the translator work load.
It also makes an attempt at dropping some misspelled words and works toward
standardizing some phrases.

This adds a command-line module named `serve` which adds a module to run the
command-line built-in PHP server with a router file that will properly
handle the expected URL dispatchers for the pages/, api/, and apps/ magic
URLs.

Usage:

$ php manage.php serve --help

This patch suggests that old attachments in the `upload_dir` can be located
and left alone when upgrading away from osTicket v1.6. Later, via the `file`
command line applet, the attachments can be migrated into the database, or
to the new filesystem plugin after it is installed with:

    php manage.php file migrate --backend=6 --to=D

This allows attachment migration to be retried in the event it failed for
any reason.

(rather than deleted after install)