fix: updated keys and configs to match identity-hub requirements

[alperbasak]

• Sadly IdHub does not play well with RSA, so updated the keys, certs and pfx using EC. (generated using KeyStore Explorer)

• jwk is generated via docker run -i danedmunds/pem-to-jwk:1.2.1 --public --pretty < cert.pem

• It is important that each connector that use IdHub, has the service url in did.json.

• Onboarding Based on the setup you are using, provider seems to be the registrator. So to register consumer for example,

curl --location --request POST 'localhost:19195/authority/registry/participant' \
--header 'Authorization: Bearer eyJhbGciOiJFUzI1NiJ9.eyJpc3MiOiJkaWQ6d2ViOmRpZC1zZXJ2ZXI6Y29uc3VtZXIiLCJzdWIiOiJkaWQ6d2ViOmRpZC1zZXJ2ZXI6Y29uc3VtZXIiLCJhdWQiOiJodHRwOi8vcHJvdmlkZXItY29ubmVjdG9yOjgxODAvYXV0aG9yaXR5IiwiZXhwIjoxNzkwOTgzNTU4fQ.c3347tllHp_6Tb4d2AjgUe0Atrps_I9HzRTaY5gK1y-wdOTyQMgwKbn6CDpVTiRi5aUdGFTDR9uhXpQ-uGx0nw'

see jwt for the payload

Then to check VCs of the consumer connector (after successful registration you should get base64 encoded JWT):

curl --location 'localhost:29191/api/identity-hub' \
--header 'Content-Type: application/json' \
--data '{
    "messages": [
        {
            "descriptor": {
                "method": "CollectionsQuery"
            }
        }
    ]
}'

see jwt for generated VC