feat: add generic did resolver

[TimoGlastra]

Add generic did resolver. Implementation is based on the did-resolver library, but uses its own did method registry for a bit more flexiblity. Parsing logic is used from the did-resolver library and it is also possible to wrap did-resolver plugins (we do that for web-did-resolver.

Supports did:sov, did:web, did:key.

Usage:

// Module
const did = await agent.dids.resolve('did:web:trinsic.id')

// or service (need to have instance of the service, class is for example)
const did = await DidResolverService.resolve('did:web:trinsic.id')

The did:key implementation comes with a DidKey class that makes it easy to use for encoding public keys as did:key string.

const publicKeyBase58 = "xxxx" // publicKeyBase58 is same as verkey
const didKey = DidKey.fromPublicKeyBase58(publicKeyBase58, KeyType.ED25519)

const did = didKey.did // get did:key string

[codecov-commenter]

Codecov Report

Merging #554 (a92476b) into main (ef6b8bc) will increase coverage by 0.47%.
The diff coverage is 93.84%.

@@            Coverage Diff             @@
##             main     #554      +/-   ##
==========================================
+ Coverage   86.30%   86.78%   +0.47%     
==========================================
  Files         288      305      +17     
  Lines        6069     6469     +400     
  Branches      896      957      +61     
==========================================
+ Hits         5238     5614     +376     
- Misses        828      851      +23     
- Partials        3        4       +1     

Impacted Files	Coverage Δ
packages/core/src/modules/ledger/IndyPool.ts	84.05% <0.00%> (ø)
.../core/src/modules/dids/resolvers/WebDidResolver.ts	58.82% <58.82%> (ø)
...e/src/modules/ledger/services/IndyLedgerService.ts	83.45% <61.53%> (-2.27%)	⬇️
.../modules/dids/domain/service/DidDocumentService.ts	83.33% <83.33%> (ø)
...rc/modules/dids/domain/verificationMethod/index.ts	89.47% <89.47%> (ø)
...core/src/modules/dids/domain/DidDocumentBuilder.ts	89.58% <89.58%> (ø)
...ckages/core/src/modules/dids/domain/DidDocument.ts	95.34% <95.34%> (ø)
packages/core/src/modules/dids/domain/DidKey.ts	98.75% <98.75%> (ø)
packages/core/src/agent/Agent.ts	97.97% <100.00%> (+0.04%)	⬆️
...es/core/src/modules/credentials/CredentialUtils.ts	98.24% <100.00%> (ø)
... and 14 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update ef6b8bc...a92476b. Read the comment docs.

[TimoGlastra]

This is ready for review now!

[jakubkoci]

That's awesome @TimoGlastra. Just a few notes but overall good 👍

[jakubkoci]

Are we sure that those deps will work with React Native?

[TimoGlastra]

I know of other react native wallets using the did-resolver library, so pretty sure this will work!

I'll make sure to do a test run to be sure!

[jakubkoci]

Does the domain have the same meaning as models in other modules? Personally, I like domain more, it seems to be used in the DDD community quite often. Should we gradually move to usage of domain instead of models?

[TimoGlastra]

Yeah I think so. I think domain has a wider scope than models, so I agree with the move to domain. 👍

[jakubkoci]

What if we call getParsed(did) inside resolve method?

[TimoGlastra]

We need to parse it on a higher level because we need to extract the did method from the did. So we could parse it in the did resolver service, not pass it and then parse the did again in the indy did resolver.