Add Pop support to wwwAuthenticateParameters

[trwalke]

Fixes #3026

Changes proposed in this request
Adding POP support to wwwAuthenticateParameters
Revising api to support multiple WWW-Authenticate headers.
Adding support for Authentication-Info headers

Obsolete apis can be replaced with apis in the column on the immediate right except for CreateFromWwwAuthenticateHeaderValue(string wwwAuthenticateValue) which is completely deprecated. Developers should use CreateFromAuthenticationHeaders(HttpResponseHeaders httpResponseHeaders) instead.

Obsolete APIs	New APIs for Multiple Schemes (returns list of parsed schemes)	New APIs for Single Schemes
CreateFromResourceResponseAsync(string resourceUri)	CreateFromAuthenticationResponseAsync(string resourceUri)	CreateFromAuthenticationResponseAsync(string resourceUri, string scheme)
CreateFromResourceResponseAsync(string resourceUri, CancellationToken cancellationToken = default)	CreateFromAuthenticationResponseAsync(string resourceUri, CancellationToken cancellationToken)	CreateFromAuthenticationResponseAsync(string resourceUri, string scheme, CancellationToken cancellationToken)
CreateFromResourceResponseAsync(HttpClient httpClient, string resourceUri, CancellationToken cancellationToken = default)	CreateFromAuthenticationResponseAsync(string resourceUri, HttpClient httpClient, CancellationToken cancellationToken)	CreateFromAuthenticationResponseAsync(string resourceUri, string scheme, HttpClient httpClient, CancellationToken cancellationToken)
WwwAuthenticateParameters CreateFromResponseHeaders(HttpResponseHeaders httpResponseHeaders, string scheme = "Bearer")	CreateFromAuthenticationHeaders(HttpResponseHeaders httpResponseHeaders)	CreateFromAuthenticationHeaders(HttpResponseHeaders httpResponseHeaders, string scheme)
CreateFromWwwAuthenticateHeaderValue(string wwwAuthenticateValue)

Testing
Unit testing
integration testing

API review

Performance impact

[jmprieur]

I left a few comments

[trwalke]

next iteration will change IEnumerable<WwwAuthenticateParameters>> to Dictionary<string, WwwAuthenticateParameters>> where string is the scheme

[bgavrilMS]

1. "token68" completely throws your parser off
2. WWWAuth and AuthInfo parsers behave differently when the header is not there
3. POPNonce is a bad name for a generic param
4. Exceptions are not specific enough.

Have you considered abandoning the custom parsing logic you have and adopting the MSAL C++ parser instead?

[bgavrilMS]

On the public API, let's follow the Cancellation Token design guidelines from https://devblogs.microsoft.com/premier-developer/recommended-patterns-for-cancellationtoken/

`It’s a good idea to only make your CancellationToken parameters optional in your public API (if you have one) and leave them as required parameters everywhere else. This really helps to ensure that you intentionally propagate your CancellationTokens through all the methods you call (#2 above). But of course remember to switch to passing CancellationToken.None once you pass the point of no cancellation.

It’s also a good API pattern to keep your CancellationToken as the last parameter your method accepts. This fits nicely with optional parameters anyway since they have to show up after any required parameters.`

So please remove oevrloads without CancellationToken and add default value to CancellationToken , e.g.

ParseAsync(string scheme, CanceallationToken = default)

[bgavrilMS]

Aproving, but please simplify public API by allowing only methods with default cancellation token (see comment)