Light EUDIW profile for Talao wallet

[ThierryThevenet]

This is a profile to support the EUDIW while keeping the Talao wallet architecture about the same. HAIP is only partly supported.

https://wallet-provider.com/distribution/guest/15

Main differences with full EUDIW stack:

• Only one WIA in the wallet with no expiration or long life WIA. (the WIA is used for wallet backend authentication behind the scene).
• No wallet key attestation (WKA), wallet uses jwt as proof of key possession
• always the same and unique key for all credentials -> No batch credential issuance support

What is very specific to this profile is :

• only P256 keys, no DIDs
• OIDC4VC 1.0 with sd-jwt and mdoc only
• The client_id must be the WIA sub attribute
• all endpoints are used with DPoP (PAR, authorization, token and credential)

PoP and DPoP should be used : #3494

the config file should look like

"customOidc4vcProfile": {
"vcdm": "1.1",
"scope": true,
"vcFormat": "ldp_vc",
"client_id": "None",
"proofType": "jwt",
"defaultDid": "urn:ietf:params:oauth:jwk-thumbprint",
"displayMode": false,
"dpopSupport": true,
"proofHeader": "jwk",
"siopv2Draft": "12",
"oidc4vpDraft": "29",
"client_secret": "None",
"oidc4vciDraft": "18",
"securityLevel": false,
"userPinDigits": "4",
"statusListCache": true,
"formatsSupported": [
"dc+sd-jwt",
"mdoc"
],
"subjectSyntaxeType": "wia_sub",
"cryptoHolderBinding": true,
"clientAuthentication": "wia",
"pushAuthorizationRequest": true,
"credentialManifestSupport": false
},