Cache InteractiveBrowserCredential

[Michael-A-McMahon]

When using interactive authentication with Azure, login with a browser may be unnecessarily repeated. This happens when a parameter which is not related to authentication changes.

For example, an access token provider accepts a scope parameter. If two tokens are requested with two different scopes, but all other parameters are the same, the browser will open twice.

As an enhancement, providers can cache the InteractiveBrowserCredential object from the first login, and reuse it to request a token with a different scope. This would eliminate the second browser pop-up in the example.