Fixes #2328

This patch shores up the new list management feature with the custom list
handler feature written to support lists being saved in a table other than
%list_item, namely the built-in ticket status list.

Also squelch the 'You sure?' popup appearing multiple times.

This adds ability to delete properties on list deletion

This is a temporary patch for v1.9.7 -- develop-next already has a better
implementation.

Add ability to import and export list items

Support using value or abbrv. for choice/selection input fields.

Add order by method to ticket status list to return appropriate sort columns
Delegate __get method in CustomListHandler to the parent list

This will allow administrator to indicate if end users are allowed to reopen
tickets in a particular closed status.

And allow for @context to add context to the bare string literal. For
instance,

    /* @trans, @context "noun" */ 'Open'

Would mark the string 'Open' translatable with context "noun".

Always save a key/value hash of the selected value(s). However, if the field
does not have the multivalue configuration setting, then retrieve just the
key with the to_php() function. to_database(), however, will always return a
JSON string with the value(s) formatted as a hash array.

Statuses with tickets cannot be deleted
Fix orm to class gracefully when joins are not inspected
Add create date to new statuses

Reserve 'archived' state for automation

Move ticket status change to unified backend.

Only cache results for ALL items

Changed Resolved to resolved state
Add ability to get statuses by states

DynamicList initial data

Add multiselect  option to selection and choices fields.