Release 0.14.0 Credential Request format is outdated

[admetaq]

Bug Report

Describe the Bug

The request body used in the Postman collection (IdentityHub → VerifiableCredential Mgmt API) and in the README is outdated.
As a result, requests fail with a 400 Bad Request error when trying to issue the FoobarCredential.

Expected Behavior

The FoobarCredential should be successfully issued when sending the credential request.

Observed Behavior

The request fails with the following error in the Consumer Identity Hub logs:

DEBUG 2025-09-11T08:38:10.482026117 [CredentialRequestManagerImpl] HolderCredentialRequest credential-request-1 is now in state REQUESTING
DEBUG 2025-09-11T08:38:10.503763743 [CredentialRequestManagerImpl] HolderCredentialRequest credential-request-1 is now in state ERROR. errorDetail: Error sending DCP Credential Request: code: '400', message: 'Bad Request'
WARNING 2025-09-11T08:38:10.503982231 A Holder Credential Request has been transitioned to 'ERROR': Error sending DCP Credential Request: code: '400', message: 'Bad Request'

Steps to Reproduce

Steps to reproduce the behavior:

1. Open the Postman IdentityHub Collection → VerifiableCredential Mgmt API folder
2. Send a credential request using the provided request body
3. Check the Consumer Identity Hub logs
4. Observe the 400 Bad Request error

Possible Implementation

Update the Postman collection and README to use the correct request body:

{
    "issuerDid": "did:web:dataspace-issuer-service%3A10016:issuer",
    "holderPid": "credential-request-1",
    "credentials": [{
        "format": "VC1_0_JWT",
        "type": "FoobarCredential",
        "id": "demo-credential-def-2"
    }]
}