Align and expand Scenarios/Business Requirements section

[Sakurann]

[Sakurann]

one from @awoie

- customer applies for VC, in-person  (pre-authz) or remote (authz code)
- wallet requests access_token/credential
- downstream process kicks off and decision needs to be made by some special officer and cannot be automated based on prior decisions/authorizations
- wallet has to wait until decision was made
- special officer makes decision
- wallet requests token/credential again and token/credential endpoint can answer with final response.

[Sakurann]

also from @awoie

Would it make sense to specifically describe the following scenarios:

• high-security in-person provisioning with/without human in the loop in downstream processes
• high-security remote provisioning with/without human in the loop in downstream processes
• high-security online presentment, same device, cross-device (if we have a good solution for that).

Would it make sense to suggest assurance levels according to eIDAS/NIST?

[Sakurann]

WG discussion:

• current section reads weird
• remove third bullet point pointing to ARF and eIDAS because they are already mentioned in the target audience section 1.1:
• rename the section and clarify it is a non-exhaustive list

Additionally supported scenarios:

Below is the non-exhaustive list of scenarios that can be realized with this specification:

- Combined Issuance of IETF SD-JWT VC and ISO mdoc
- Both issuer-initiated and wallet-initiated issuance
- Issuance and presentation of Credentials with and without cryptographic holder binding