open/close toggle and fields in different forms - fixes #5659

Ticket.is_creator_vlidated? now actually fetches the user from the db and returns false if it does not exist.

email and regarding user fields can be set to defaults based on
created_by user.

If these fields are emptied by the submitting user they will be set to  whereas they are nil if they have not been initialized. In that case we will use meaningful defaults from the user who created the ticket.

We should respect the users choice. We can still get their email from the user id if we really need to.

They do not save any changes. So i think it's better to keep them separated from the Save button that does save changes.

the loading... text on the buttons was not capitalized before.

So in order to change this in a (more or less) single place i added
new button types to simple_form:

button :wrapped - normal button, with loading and an optional cancel button wrapped in the classical bootstrap action div.
    cancel option contains the url to go to when canceling.

button :loading - simple button with loading text capitalized by using i18n (simple_form.buttons.loading)

Conflicts:
	engines/support/app/views/tickets/new.html.haml

Feature/api quota support + current_user null pattern

when rendered from teh create action due to an error user_id param will
sometimes be an empty string. We should still avoid rendering the
navigation because the path's can not be resolved without a user_id.