Support Microsoft Entra Id authentication for rest source

[yao-msft]

Change

This pr adds Microsoft Entra Id support for rest source. To achieve this, rest source /information contract is updated with below. The /information endpoint should never use authentication as it is the first handshake between winget client and rest source.

// "Authentication": {
//     "AuthenticationType": "microsoftEntraId",
//     "MicrosoftEntraIdAuthenticationInfo" : {
//         "Resource": "Resource",
//         "Scope" : "test"
//     }
// }

Rest source interface will read this info and acquire authentication using WebAccountManager OS api during all following source interaction (/packageManifests, /manifestSearch)

CLI arguments updated to specify authentication behavior

COM interface updated to specify authentication behavior from caller and provide authentication info of package catalog to caller

Validation

• Due to lack of e2e rest source tests and complex in getting real Microsoft Entra Id token. E2e validation is manually performed. I tested cli (packaged and unpackaged), InProcCom and OutOfProcCom . Both interactive and silent flow works correctly. I setup a test rest source with Microsoft Entra Id protection (based on tenants) and it's working as expected
• Added a bunch of unit tests: AuthenticationInfo parsing, RestClient and RestInterface creation, and RestInterface GetManifest and Search operation with override Microsoft Entra Id token

Microsoft Reviewers: Open in CodeFlow

[denelon]

• Entra ID Authentication for WinGet REST sources #4124

[yao-msft]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ryfu-msft]

m_authArgs.AuthenticationAccount.empty()

Does an empty authenticationAccount mean that it succeeded?

[yao-msft]

Empty m_authArgs.AuthenticationAccount means user or caller did not specify which account to use. So we consider it as authentication success as long as WebAccountmanager returns success.