Removed scopes param from IProvider.GetTokenAsync

[shweaver-MSFT]

Fixes #

PR Type

What kind of change does this PR introduce?

• Bugfix

What is the current behavior?

WAM doesn't support incremental consent, so this function is deceiving. Only pre-authorized scopes will return a token successfully, in which case they should be included with the rest of the scopes provided during provider construction.

What is the new behavior?

I've removed the scopes param from IProvider.GetTokenAsync.

PR Checklist

Please check if your PR fulfills the following requirements:

• Tested code with current supported SDKs
• Sample in sample app has been added / updated (for bug fixes / features)
  • Icon has been created (if new sample) following the Thumbnail Style Guide and templates
• Tests for the changes have been added (for bug fixes / features) (if applicable)
• Header has been added to all new source files (run build/UpdateHeaders.bat)
• Contains NO breaking changes

Other information

Docs PR: MicrosoftDocs/WindowsCommunityToolkitDocs#542

[ghost]

Thanks shweaver-MSFT for opening a Pull Request! The reviewers will test the PR and highlight if there is any merge conflict or changes required. If the PR is approved we will proceed to merge the pull request 🙌

[shweaver-MSFT]

Code is done, CI passed. Waiting on docs PR

[shweaver-MSFT]

Merging in. We'll get the docs updated before the preview release in the next few weeks.