The ThreadEntry::normalizeFileInfo() method is called from ::create(), but
before the thread entry is saved. Therefore, the ::getThread() and
::getObject() methods will likely not return a valid object for posting the
thread message.

Fix a bug where it was impossible to disable ALL collaborators
Change recipients active/total count on update

This commit attempts to remove some of the confusing and redundant code to
attach files to thread entries and replace it with a single code base. It
also attempts to remove and error where a single attachment might be
attached to a new thread entry multiple times.

Lastly, it removes the insert followed by an update for emails with inline
images. This should improve performance processing emails as only one trip
to the database is now necessary for thread entries with inline images.

This pass also makes a stride at adding correct punctuation and making error
phrases consistent.

Previously, the create method was used to create a new instance of an orm
model (which would later result in an INSERT when persisted); however, some
classes require or utilize varying parameters to their create() method,
which PHP7 considers an error. Methods in subclasses must be defined with a
calling signature compatible with the parent class.

This patch shifts the concept of model creation to the constructor. Now, the
constructor of ORM models is required to be compatible with that of
ModelBase class. Now that most models do not define a constructor, this is
much easier to control, and much more logical.

Also, remove an issue where assignments on a relationship field to an
instance of a super class of the foreign model would raise an error. This
was previously addressed by re-classing the instance in the
ModelInstanceManager::getOrBuild(); however that design would create
multiple instances of the same object in memory, which defeats one of the
primary design concepts of the ORM. This patch addresses the issue by
allowing super-classes of the declared foreign model in relationship
assignments.

This commit attempts to remove all coding standard warnings emitted by PHP
7.0.

Let textarea widgets parse and clean input based on configured text format.
Add cleanup routine to ThreadEntryBody
Clean response/note inputs

Conflicts:

	include/class.forms.php
	include/class.ticket.php

This is commit reverts prior commit to prevent email loops by dead-banning
alerts and auto-responses based on recent communication with the end user.

Add a global option to disable avatars on thread correspondence . Agent's
and user's profiles will still show an avatars.

Add a preference option to set the sort order of the thread entries in DESC or
ASC order.

 * System Default order is ASC
 * Auto-scroll is disabled when sort order is set to DESC.

Add preference to agent's profile to enable relative time use.

Let textarea widgets parse and clean input based on configured text format.
Add cleanup routine to ThreadEntryBody
Clean response/note inputs

Make sure the references are valid for the email recipient.

This is necessary to differentiate true system notes vs. notes made by a
deleted agent or collaborator.

getObject should be used instead.

Disable sorting on ThreadEntry::email_info__mid lookups for email processing
which results in an on-disk temporary table.

Fix case where collaborators were not being alerted
Alert admin last on new ticket - just in case admin email is used by an agent.

This patch changes the way the thread entry type and other properties are
determined by using the userClass determined in the Mailer::decodeMessageId
method which is preferred over the older heuristic methodology using the
`From` email address alone.

Only send one autoresponse to the same user for new messages sent in a five
minute window per thread. This will stop looping because of bounces and OoO
notifications not flagged as autoreplies

Redirect to recent queue / listing on transfer or assign

And two flags, one which signals that stored HTML is correctly balanced and
does not need to be balanced when rendered in the ticket view. The second is
used to signal messages received from collaborators.

Additionally, this patch fixes showing external inline images (via the [Show
Images] button) when clicked.

Initially, include support only for Gravatar

getVar() is now called first, then object properties and array properties
are considered, and then getTag() is considered if none of the other options
work. This allows for more predictable results using the variable
replacement system, and allows ::getVar() to override every other means to
use variables in email templates.

This adds the concept of independent multi-thread rendering