[Feature] Separate Graph SDK interaction into own package

[shweaver-MSFT]

Describe the problem this feature would solve

I don't want the bloat of the entire Graph SDK if I only need to do authentication.

Describe the solution

The Graph SDK isn't really needed for authentication. There is a smaller Graph.Auth package we can use to get the core constructs to enable the sign in flow to work. The rest of the Graph SDK consumption should be relegated to a separate package, Microsoft.Toolkit.Graph.Data (or something similar), upon which the other packages can depend on as needed.

Microsoft.Toolkit.Graph.Data

This package will manage how we leverage the Graph SDK and interact with the Graph APIs.

In addition, the Graph SDK occasionally has bugs. A layer of indirection will allow us to workaround any issues while maintaining a consistent usage pattern across the solution.

Describe alternatives you've considered

Additional context & Screenshots

[ghost]

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 🙌

[shweaver-MSFT]

This was changed in PR #76.

Now the main CommunityToolkit.Net.Authentication package no longer relies on the Graph SDK. All Graph SDK interaction is relegated to the CommunityToolkit.Net.Graph package