Add built-in support for Oidc tokens

[AlexF4Dev]

The pull request adds support for OIDC access tokens. It uses PKCE flow to acquire tokens - no stored secrets required. The tokens are cached, and refresh token is used when the access token is expired. It can be used with any identity provider which supports PKCE OpenID Connect flow.

Example for Google:

GET https://openidconnect.googleapis.com/v1/userinfo
Authorization: Bearer {{$oidcAccessToken clientId:786371393912-ahu1p5p81n2pj4fa90bo33pirr1mroeu.apps.googleusercontent.com callbackPort:7777 authorizeEndpoint:https://accounts.google.com/o/oauth2/v2/auth tokenEndpoint:https://oauth2.googleapis.com/token}}
Accept: application/json

Example for Microsoft:

GET https://graph.microsoft.com/oidc/userinfo
Authorization: Bearer {{$oidcAccessToken clientId:336c0138-03e7-4183-a398-3e63445dd5f5 callbackPort:7777 authorizeEndpoint:https://login.microsoftonline.com/consumers/oauth2/v2.0/authorize tokenEndpoint:https://login.microsoftonline.com/consumers/oauth2/v2.0/token}}
Accept: application/json

The example will call an API with google access token. For google the app should be registered as UWP to use PKCE without the client secret.

[Huachao]

@AlexF4Dev please check these alerts

[AlexF4Dev]

@AlexF4Dev please check these alerts

The first alert is probably false positive, because this is not a webapp. I have fixed regex warnings.

[Huachao]

remove extra whitespace in description

[Huachao]

remove extra whitespace between access modifier public and method name in this file

[AlexF4Dev]

Trust nobody even IDP :-). I have added sanitizeHTML to prevent the script injection. Do we need support for DPOP/MTLS? It could be used to access API's protected by FAPI.

[Huachao]

@AlexF4Dev Merged, thanks