[Feature] GraphPresenter should react to global provider state changes

## Describe the problem this feature would solve

The `GraphPresenter` requires an `IBaseRequestBuilder` implementation to determine what data to fetch from Graph. We don't currently have a good way to define the `RequestBuilder` property in XAML, so this must be done from code. The problem is that if the provider state changes after the `RequestBuilder` property is set, the `GraphPresenter` will fail. The way to fix this is to nullify the `RequestBuilder`, and then re-set it.

## Describe the solution

Update the `GraphPresenter` to listen for changes in the global provider state, and do whatever is required to keep the control functional after a login change.

The `GraphPresenter` should not display any content if the global provider is not signed in.

## Describe alternatives you've considered

None

## Additional context & Screenshots

All of this code is required to support a single instance of the `GraphPresenter` control:

```csharp
namespace SampleTest.Samples.GraphPresenter
{
public sealed partial class MailMessagesSample : Page
{
public IBaseRequestBuilder MessagesRequestBuilder { get; set; }

public MailMessagesSample()
{
this.InitializeComponent();
ProviderManager.Instance.ProviderUpdated += OnProviderUpdated;
ProviderManager.Instance.ProviderStateChanged += OnProviderStateChanged;
}

private void OnProviderUpdated(object sender, IProvider provider)
{
if (provider == null)
{
ClearRequestBuilders();
}
}

private void OnProviderStateChanged(object sender, ProviderStateChangedEventArgs e)
{
if (e.NewState == ProviderState.SignedIn)
{
var graphClient = ProviderManager.Instance.GlobalProvider.GetClient();

MessagesRequestBuilder = graphClient.Me.Messages;
}
else
{
ClearRequestBuilders();
}
}

private void ClearRequestBuilders()
{
MessagesRequestBuilder = null;
}
}
}
```

```xml

...

```

Inizia con il controllo GraphPresenter e la gestione di RequestBuilder, quindi esamina gli eventi provider e provider-state di ProviderManager utilizzati nell’esempio MailMessagesSample. Traccia cosa accade quando il provider cambia o viene effettuato il logout; il lavoro è completato quando il controllo rimane funzionante dopo le modifiche all’accesso e non visualizza contenuti quando l’utente ha effettuato il logout.

Scritto dal modello di indicizzazione a partire dal testo della issue.