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.

Filter members based on department's assignment restriction when building a
list of assignees.

Add a checkbox option within the department setting to disable the "Claim on
Response"

Feature must be enabled globally in order to be disabled locally (duh!)

Department/Topic create now considers the possibility of preset id (primary key)
Default help topic routing to floating system's default department

* Set all "route department" filter actions to "unchanged"
* Fix bug in quick-add code where new option was not properly added

Reset permissions and change primary department and role

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 is required with the connection to Dept::getEmail()->send(...)

The bug was partly due to switch to ORM.

* Fix crash saving a page (regression)
* Fix red banner deleting a department
* Fix crash deleting a knowledgebase article

If a relationship has more than one field in the constraint, then the
InstrumentedList query generated would not be correct. This happens often
in osTicket for the join foreign key fields `object_type` and `object_id`.

This patch addresses the issue by sending all the fields in the foreign key
to the InstrumentedList constructor.

Add support for passing a criteria to AssignmentField to limit  the choices
Limit assignees based on department settings
Cache choices

Unassign tickets on transfer when the target department has assignment
restriction and the assigned staff is not a member.

Disable claim (quick self-assignment) when above restriction is in effect.

  * Fix fatal errors adding a new FAQ (fixes #1648)
  * Fix removal of attachments when deleting a thread (fixes #1650)
  * Fix crash discovering department members for alerts (fixes #1652)

This patch adds a ::getAlertEmail() method to the Department class, which
allows administrators to use the department email address (normally for
replies) as the alert email address. If not specified, the system alert
email address is retrieved instead, automatically.

Support duplicate names in different hierarchy
Save path on add/update
Show full department name on transfer

The commit also renames some fields in department table.

The commit also renames some fields in department table.

Lint test rulez!

This significantly reduces the time necessary to render the ticket queue
page with the ORM.