OAUTH2.0 authorization code grant in API description

[DT-DawidWroblewski]

Problem description
According to issue #53 from commonalities we should use the OIDC security scheme for NumberVerification API.

There is an inconsistency inside yaml between the description & UML that points to OAUTH2.0 authorization code grant flow.

It is either OAUTH2.0 or OpenID Connect (with ID Token delivered in token response).

Expected behavior
Description that meets requirements from Commonalities - OpenID Connect flow described within UML & API description (yaml)

Alternative solution
If we think that we should use OAUTH2.0 Authorization code grant alternatively - we should apply changes in yaml and promote them inside commonalities.

Additional context

[DT-DawidWroblewski]

discussion continues here: Issue#90 Identity & Consent Management