Add ability to login to Azure account for provisioning and publishing

[benbrown]

Add the ability to sign-in to an Azure account, thus making it possible to take actions on the user’s behalf such as creating and publishing to Azure resources.

A login to Azure will not be required to use Composer. It should continue to be possible to install an authentication plugin (such as AAD) to gate access to Composer and provide the user info context.

We should strive to implement this in a way that could be used by other plugins as well - for example, attaching a Github login to allow publish to Github. This will require some extensions to the current auth plugin system. Details here: #3390

Describe the solution you'd like

• Get design input from @sangwoohaan and @mareekuh
• Provide a login button that will allow the user to trigger the login process (needs design!)
• If logged in, show some status indicator (username?) and a logout button (Needs design!)
• Upon login, capture the Azure access token, refresh token, tenant id, and metadata necessary to request a new token when it expires
• Automatically refresh the token if expired
• Require an active Azure login when using the “publish to target” tool
• Require an active Azure login when using the provisioning tool

Additional context

This will require us to be a “First party app” which is described here:
https://identitydocs.azurewebsites.net/static/aad/first_party_decision_guide.html
This is how we achieve the same functionality in Emulator.