Do not set new login from application form when user found while approving.

 - case: user joined identities after sending application
 - notifications: if user known, get login from attribute instead of application (if attribute not empty)
Registrar: do not create application when password reservation fails.
 - GUI: fixed text in exception message
Registrar: notifications to VO admins are now by default 'en'.
 - Optionally based on attribute value for VO/Group.
 - Return RegistrarException to show raw message in GUI when approving application
Registrar: fixed transactions above createApplication()

 - method createApplication() separated in two methods
 - createApplication() is no longer transactional and does verification and approval only if creation succeed
 - createApplicationInternall() is transactional and do not verify and approve application
 - throw RegistrarException from createApplicationInternnal() + rollback on ApplicationNotCreatedException
 - add new notification type APP_ERROR_VO_ADMIN
   (used when automatic approval fails to notify vo/group administrators)
 - moved code for sending verification mail to ensure correct order of recieved
mails
 - GUI - added new app mail type
Registrar: fixed login check/reservation

 - fixed case, when user and his logins were new, but considered as already in use and unreserved from KDC

Correct logical order when approving any application is now
 - set all non-login attributes
 - create member / add to group
 - unreserve new login, if user already have login in same namespace
 - set login attributes, which are purely new
Registrar - fixed typo in method name createApplicationInternal()
Merge pull request #33 from zlamalp/registrar_login

Registrar: fixes for login handling and transactions