Provide failsafe for a client's name

It is possible that a recipient received and processed by the system may not
have a name set. In that case, the email mailbox should be used. As a
failsafe, avoid crashing if the User::save() should fail.
Don't clobber custom data for new clients
Add import feature to user directory and organization
Fixup user import via cli
orm: Make __get() and get() consistent
Fallback to client email display on user directory
Simplify header detection logic with outdent
Merge pull request #790 from greezybacon/feature/user-import

Reviewed-By: Peter Rotich <peter@osticket.com>
Add CrossTabQuery and move DynamicDataView  to DynamicForm class

This is necessary to allow for other form types to use dynamic data
view/export
Add support for user data export
Add export routine to TextareaField

Sanitize textarea content on export
Add ability to pass output file to result set exporter

This is necessary in case the exporter wants to redirect output to a file.
Use built-in PHP functions to encode and output CSV content
Support organization export
Show account manager on org profile