This adds a feature for remote authentication methods for clients, such as
LDAP, which will, after successful authentication, yield a
ClientCreateRequest rather than an AuthenticatedUser. The
ClientCreateRequest represents a successful authentication and user
information lookup for a remote client. The client is then presented with a
registration page where their information for their account in the local
system can be reviewed prior to the account creation. Once created, the
client account is confirmed without an email confirmation and is logged in
immediately without reentering a password.

This make writing new backends (such as LDAP) easier and less copy+pasting
is required.

Now it looks more like the email templates management page.

If the help desk administrator has enabled requirement of login to create
new tickets and has also disabled account registration, then new tickets
cannot be created via the web portal.

Otherwise, it might be possible for a forwarded email to accidentally
contain a ticket link, with which a sinister individual might be able to use
to register for account on behalf of the original client, and, at the same
time, be able to change the user's email address to his/her own.

This will be triggered if the client follows a link from an email And the
help desk administrator has enabled the setting to require a login to create
a  ticket.

Client accounts now that the user is verified either via staff or the
client's email mailbox, there's a much lower risk to showing a verified user
other tickets and virtually no reason that an administrator should have to
turn the feature on.

This is the mode of the system if account registration is disabled

Instead of always showing the tickets page

For client account / profile updates

Add client registration methods and login required checkbox