Integrated AAD support

[shweaver-MSFT]

Fixes #116

PR Type

What kind of change does this PR introduce?

• Feature

What is the current behavior?

Currently WindowsProvider only supports authentication of consumer MSA accounts.

What is the new behavior?

This PR introduces new authentication support for organizational AAD accounts.

The WebAccountProviderType enum has a new Aad value that can be used to specify that only organizational accounts should be available to the user. Configuration in AAD is required to support authentication of organizational accounts.

I have also added a new WebAccountProviderType.Local option which uses whatever the active local account is. When using Local, configuration in AAD and a Store app association is required for the app to work consistently. If only MSA/AAD is meant to be supported, the appropriate WebAccountProviderType.Msa/Aad should be specified in the WebAccountProviderConfig provided during initialization.

Lastly, the WebAccountProviderType.All enum value has been updated to WebAccountProviderType.Any. Similar to Local, using Any requires configuration in Azure AAD as well as a Store app association in order to support which ever account types could be available.

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

[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 🙌