Closes #5376

Additionally:
- Returns an error for invalid domains (on registration)
- Moves "insertOrUpdateUser" method code to a function

- Bypass user registration validations for livechat users - Closes
  #2276, #1963

- Set livechat count and order to zero when empty

- Pick a livechat departament if none select and there is more than one

- Fix livechat warning hide message

- Add autolinker to livechat

Replace placeholder in enrollment email subject

* Add function to handle errors

* Delete message errors

* handle error for hideRoom

* Allow returning error instead of calling toastr.error

* Handle error for leaveRoom

* handle error for openRoom

* handleError for toggleFavorite

* handleError in updateMessage

* error for samlLogout

* handleError for assets

* Add global handleError to eslint

* handleError for addOAuthService

* handleError: getUserRoles

* handleError: insertOrUpdateUsere

* handleError: messageDeleting

* handleError: removeUserFromRoles

* handleError: addPermissionToRole

* handleError: addUserToRole

* handleError: deleteRole

* handleError: removeRoleFromPermission

* handleError: removeUserFromRole

* handleError: saveRole

* Return ready on publish without permission

* handleError: channel-settings

* handleError: mailMessages

* handleError: fileUpload

* handleError: rocketchat-importer

* handleError: addIncomingIntegration

* handleError: deleteIncomingIntegration

* handleError: updateIncomingIntegration

* handleError: addOutgoingIntegration

* handleError: deleteOutgoingIntegration

* handleError: updateOutgoingIntegration

* Return ready on publish without permission

* handleError ldap

* remove throw from client code

* handleError: setEmail, slashCommand

* Sort en.i18n.json

* Google translated languages

* Use correct error return from publishes

* RateLimiter.limitFunction

* Fix order of error "500"

* handleError validateEmailDomain

* handleError channelSettings; settings

* handleError livechat

* handleError: Mailer.sendMail

* handleError pinMessage and unpinMessage

* handleError messageStarring

* handleError oauth apps

* handleError: saveNotificationSettings

* handleError getRoomRoles

* handleError: createDirectMessage

* handleError saveUserPreferences

* handleError: saveUserProfile

* handleError sendConfirmationEmail

* Add ecmascript to root

* handleError: avatar

* handleError: getStatistics

* handleError: roomSetting

* handleError: channelSettings

* handleError: sendInvitationEmail

* handleError: addUserToRoom

* handleError: uploadedFilesList

* Change error key on user edit

* handleError: userInfo

* handleError: userRegistration

* handleError: createChannel

* handleError: createPrivateGroup

* handleError: setUserPassword

* handleError setUserActiveStatus

* handleError: accoutns

* A few more errors thrown

* Error: livechat publishes

* Errors in methods

* handleError searchAgent

* Add errors handling

More errors handling

Auto-translation for all languages

* Permalink

* New field 'type' for users

* Show only default room types on Admin > Rooms

* Rename migration 40 to 41

restrictCreationByEmailDomain accepts either a function or a string.
When it is a string, it will be used by some of the OAuth integrations
(like google) to proactively restrict logins.

For my use case this means that employees are automatically asked by
google to login with their work credentials instead of first having to
select between their personal and work accounts.

The current regex for checking restricted domains is not escaped and can
be easily tricked. For example, if the restricted domain is
"example.com", we currently accept "tester@hackedexample.com".

This change forces the full domain to be correct, and also escapes it to
prevent metacharacters from causing false matches.

Setting allows admin to modify Meteor.loginTokenExpires from default 90 days to something else.
Server restart is required for this setting to take effect.
Default value is still 90 days if not modified by admin.