And add translations for the draft mechanism

Also add some logic to the POT builder to warn about incorrect arguments to
the __() function and friends as well as warn about _() usage.

The software defines at least three contexts for the phrase "Open"

  * The name of a ticket queue (Open tickets)
  * A status of a ticket (Open / Closed)
  * An action to be performed (Open a ticket)

References:
(Crowdin login required)
http://i18n.osticket.com/translate/osticket-official/148/enus-de#2915

Also, the final version of the system will not require the `gettext`
extension for PHP

Also add several lint fixes for packaging

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

Instead of allowing the backend to send a redirect URL, which doesn't make
sense on the command line

Add CLI import/export support for organizations

Output headers on export

Implement CLI user import/export in a well formatted CSV file. Name and
email address are the only supported fields at the moment.

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.