If a user is created with an empty domain name (e.g. <user@>), then the user
would be associated with the first organization without a main domain
specified.

This patch ensures that the domain is not empty when making a match with an
organization.

Allow usage of something like `%{ticket.user.organization.var}`

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".

Add other locations as well a failsafe for the htmlentities() call

Auto assign tickets to organization's account manager only if the flag is set and as
the last resort i.e topic or filters assignment takes precedence.

Allow developers to specify a sorting position for groups of fields
selectable in the criteria select drop-down

Make the organization page happy!

Use .domain.tld to accept all subdomains of a parent

This is a slight edit over the previous implementation of the same feature.
Previously, an "account" was required, which implies a user account with a
password. This implementation simply requires a user record. Importing of
users by organization domain is still supported -- even if the user does not
yet exist.

Previously we required an account to associate a user to an organization.

Deleting an organization with users will simply orphaned the users.

Don't save 'name' as dynamic data for organization form.

Add organization class