Support DIDCommV1 legacy service

[conanoc]

PeerDIDHelper already had PeerDIDServiceLegacy which was the service type of DIDCommV1, but recipientKeys property was missing.

This change allows PeerDIDHelper to create a numAlgo 2 peer-did with the legacy service. This has been tested with the Credo-ts to do did-exchange protocol which exchanges numAlgo 2 peer-dids.

[beatt83]

Hi @conanoc. First thanks for contributing it means a lot. :)

I understand the changes you're making and your right. But I don't think this changes should come in here besides the routingKeys.

I need to change DID Core library so the Service is a AnyCodable and then you can insert extensions to the json, so this specific case you have will work then.

Let me see what I can do around this today and tomorrow and come back to you.

[beatt83]

@conanoc can you check this? #8

With this you can add any extension to the service or serviceEndpoint, I see DIDCommV1 uses as well priority with this changes that is possible.

[conanoc]

#8 Looks perfect. Thanks!