Move relevant verifier endpoints from sign and verifier to verifier service

[kayaelle]

• Implement the VC-API /credentials/verify endpoint. Feel free to look at the existing implementation in sign-and-verify. Note that you'll want to be using the https://github.com/digitalcredentials/issuer-registry-client for this, instead of axios.
• Implement the VC-API /presentations/verify endpoint. Feel free to look at the existing implementation, same thing re issuer-registry-client instead of axios.

[kayaelle]

@dmitrizagidulin - do we still need to do this?

[jchartrand]

@kayaelle @dmitrizagidulin

This coincidentally came up earlier in the week - if we want to satisfy the verifier part of the VC Test Suite (https://github.com/w3c/vc-test-suite-implementations/) then we’d want to set up a verifier-service. Dmitri pointed out that this should be very easy to do. Just a couple of endpoints that directly call the verifier library.

[jchartrand]

I've implemented the credentials/verify endpoint and deployed it to test-issuer.dcconsortium.org/verify and will shortly submit a PR to have it show up in canivc.

We will also, though, want to update this service to support the eddsa-rdfc-2022 suite, which will be done as part of refactoring our verification logic into a single library for use across LCW, VerfierPlus, this test verifier, the ORCID POC, and any embeddable verification component we might make.

See:

openwallet-foundation-labs/learner-credential-wallet#367
openwallet-foundation-labs/learner-credential-wallet#656

[alexfigtree]

#1 deployed to test issuer and canivc (but canivc does not test for #2) - waiting on shared verification package