Problems in Authorization Code with scope and mutliple Credential Datasets

[paulbastian]

Imagine a basic scenario where a Wallet wants to request multiple Credentials with different Credential Datasets, e.g. multiple ePrescriptions. The challenge is how a Wallet knows how many Credential Requests to do.

Within Authorization Code Flow with authorization_details, the Wallet can deduct the number of Credential Datasets from the Token Response with credential_identifiers array size.

Within Authorization Code Flow with scope, this method does not work (as it is specific to authorization_details) and the Wallet may need to send requests until it gets an error, which seems to be insufficient.

Proposal could be to allow credential_identifiers for all flows. Changes discussed in #294 are also relevant.