[Feature] LoginButton should fire events in response to GlobalProvider changes

[shweaver-MSFT]

Describe the problem this feature would solve

Currently the login button will emit a LoginCompleted event when a user explicitly clicks it to login. However, if the user login happens silently/automatically, then the button events don't fire.

Describe the solution

Enable the LoginButton to emit login events in response to global provider changes, even if the user doesn't explicitly interact with the button.

Describe alternatives you've considered

Additional context & Screenshots

Hello shweaver-MSFT, thank you for opening an issue with us!

I have automatically added a "needs triage" label to help get things started. Our team will analyze and investigate the issue, and escalate it to the relevant team if possible. Other community members may also look into the issue and provide feedback 🙌

This issue has been marked as "needs attention 👋" due to no activity for 15 days. Please triage the issue so the fix can be established.

This issue has been marked as "needs attention 👋" due to no activity for 15 days. Please triage the issue so the fix can be established.

[shweaver-MSFT]

The best we can do here is fire the Login/Logout-Completed events in response to global provider changes. We can't really do anything with the Login/Logout-Initiated events because the ProviderEvents are not granular enough to tell us HOW we are transitioning. The ProviderState enum only supports SignedIn, SignedOut, and Loading.