Adds raiseEvent parameter to getUser() method

[waldemarennsaed]

Description

Relates to #712 and provides a solution that is backwards-compatible and will fix an issue for some users.

Adding a new parameter raiseEvent = false to the UserManager.getUser() method to allow execute the addUserLoaded() event handlers after raising the userLoaded event.

Background: The userLoaded event does currently not get raised whenever the user value is being read from the local storage, which happens whenever no user data has to be fetched from the authority but from the store. In #712 developers complained about this behavior since some business-logic depends on the getUser()/userLoaded method/event for .e.g. loading additional user-related data from third-party sources like APIs. In the case that a user is already authenticated and e.g. reloads the page, the storage provides the getUser() data but does not raise the userLoaded event anymore. That will break the described business-logic and must be avoided with a workaround, e.g. using Proxy() which is not preferred as the optimal solution (see #712 (comment) for an implementation example with Proxy()).

This solution allows raising the event on purpose whenever the parameter is set to handle further business logic after checking for a users authentication.

Tests

Added unit-tests for the new parameter which is by default set to false.

[waldemarennsaed]

@pamapa any thoughts on this?