WindowsProvider uses deprecated range separator

[Richasy]

Describe the bug

In WindowsProvider, use , as scopes separator, while in graph documentation, space is recommended. This problem will cause the AAD account to fail to authorize when requesting multiple permissions.

• Is this bug a regression in the toolkit? If so, what toolkit version did you last see it work:

Steps to Reproduce

Steps to reproduce the behavior:

To reproduce this error, you need to prepare an AAD account and grant two or more permissions

1. Enter ClientId and two or more scopes according to the documentation
2. Click the Login button to log in to your AAD account
3. See error

Expected behavior

Can request multiple permissions normally.

Environment

NuGet Package(s): 7.1.2

Package Version(s): 7.1.2

Windows 10 Build Number:
- [ ] Fall Creators Update (16299)
- [ ] April 2018 Update (17134)
- [ ] October 2018 Update (17763)
- [ ] May 2019 Update (18362)
- [x] Insider Build (build number: 22000)

App min and target version:
- [ ] Fall Creators Update (16299)
- [ ] April 2018 Update (17134)
- [x] October 2018 Update (17763)
- [ ] May 2019 Update (18362)
- [x] Insider Build (22000)

Device form factor:
- [x] Desktop
- [ ] Xbox
- [ ] Surface Hub
- [ ] IoT

Visual Studio 
- [ ] 2017 (version: )
- [ ] 2019 (version: ) 
- [x] 2022

Additional context

It's a bit quirky, but when using , MSA works fine and AAD fails. With spaces, both work fine

Hello Richasy, 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 🙌