the library should handle calls for multiple interactive logins internally

[tachtevrenidis]

Currently, it seems like if there is a request for interactive logins while another interactive login is on the screen the library throws:

MSALErrorCode.interactiveSessionAlreadyRunning

I think that if the call for interactive login was for the same exact resource and scopes, the library should hold up the second call, wait until the first is done, and return the same token to the second one.

Currently I have to resolve this with semaphores inside the app.