This feature extends the ability to mark tickets as Answered/Unanswered to
any Agent with the Role Permission to Post Reply in the Department. This
also adds the ability to add an (optional) Internal Note when marking as
(un)answered.

Field: Help Topic Forms

Don't show fields disabled by help topic
Pass create mode for pre-selected help topic forms

Forms: Field Permissions

issue: FAQ/Page Attachments

This commit addresses inconsistencies on how field edit rights and
visibility are are handled.

This addresses an issue where inserting images on a Page or FAQ and having
the setting enabled for "Login required to view attachments." does not
display the images at all when the Page/FAQ renders in view. This is due to
the Page/FAQ update functions that were not updated to fit the new
`id=>name` format for `keepOnlyFileIds()` introduced with `f179cf15`.

issue: Email Default Dept

issue: create_date Variable

This addresses an issue where the create_date variable is showing as Unix
timestamp instead of formatted date. This was due to a typo introduced in
commit `8623ed60` where the `$format` argument was forgotten for
`Format::datetime()` in the `FormattedLocalDate::getVar()` method.

This addresses an issue where configuring a System Email to have a
Department and then editing/saving changes on the configured Department will
change the System Email's Department back to the the default Department.
This was due to a un-needed Department Status check introduced with commit
`1d361b51`. This also updates all instances of Dept Status comparison to be
case insensitive and non-translated.

Deleting the Default Queue

queue: Top-Level Ticket Counts

FileUploadField Validation

This commit fixes an issue where Agents were able to delete their default queue which then prevented them from going to any queue upon logging in. Now, they will see an error message if they try to do so.

Status Column: Fix display and sorting

This adds a setting in the Ticket Settings to give the option of showing the
ticket counts on Top-Level queues. If enabled, this will populate the ticket
counts next to the Top-Level queue names like they used to be. The only
caveat is the counts are triggered by mousing-over any of the queue names as
we only load the counts when we need to display the sub-queues (for better
performance).

This also adds a new format function called `number` (Phase 1). As of now it
will format any integer to a comma separated number (eg. `1337 -> 1,337`).

Dashboard Statistics Issue

This commit addresses an issue where we lost the logic for needed GROUP BYs in the dashboard report. They were added back for the Statistics query but not for the query that calculates Response and Service time. This now adds it back.

issue: Queue sort_id

This commit addresses where wrong "primary" field was used to indicate
Ticket Status column. It also fixes an issue where sorting was done via `id`
instead of `name`.

This commits adds a flag to skip validation on $field->getClean() routine.
This is necessary to allow FileUploadField to fetch "injected" files.

This addresses an issue where poor little `sort_id` was sadly forgotten for
the two main-level queues "Open" and "My Tickets".

issue: ticket_link Fatal Error

Queue counts

This addresses an issue where replying to a ticket causes a Fatal Error for
the system. This is due to the `$ticket` object not being set before the
else statement therefore causing the `getId()` function to fail. This breaks
down the if/else statement to make sure the `$ticket` object is in-fact set
before continuing.

Dashboard Statistics Issue

This commit fixes an issue where we were not able to see all of the departments, topics, and agents that should have been included in the report. The logic for the  GROUP BY in the queries was changed, so we just manually added them back in.

This commits adds fallback for queue counts and improves caching mechanism.

issue: Dupe Page Requests Fix

Add new API headers to whitelist

upgrade: Actually re-fetch the config from database

issue: Delete User Error

This addresses an issue reported on the forum where deleting a User will
throw a fatal error. This was caused by 4558 where the `state` column was
mistakenly overwritten with `event_id`. In addition, this changes `$deleted`
to `$status_id` for better readability.

issue: Export Event State Error

This addresses an issue where export does not work due to a fatal error
"Unknown column 'R0.state' in 'where clause'". This was caused by 4558 due
to the removal of enums and the `state` column. This updates the filter to
match the `event_id` instead of `state`.