Feature/native did web resolver

[domwoe]

Add native did:web resolver. Carved out and touched up from #1143

• Uses DID and DID Doc validation from pyDID
• Does not support encoding of ports in DIDs yet (e.g. did:web:localhost%3A8443 -> https://localhost:443/.well-known/did.json yet, because pyDID does not allow '%' char in DID (See: Allow % char in DID Indicio-tech/pydid#34)

[codecov-commenter]

Codecov Report

Merging #1218 (84035ce) into main (1c7bc86) will decrease coverage by 0.05%.
The diff coverage is 67.39%.

@@            Coverage Diff             @@
##             main    #1218      +/-   ##
==========================================
- Coverage   98.47%   98.41%   -0.06%     
==========================================
  Files         456      457       +1     
  Lines       25428    25474      +46     
==========================================
+ Hits        25039    25070      +31     
- Misses        389      404      +15     

[andrewwhitehead]

Please reorder imports:

import urllib.parse

from typing import Sequence, Pattern

import aiohttp

from pydid import DID, DIDDocument

from ...config.injection_context import InjectionContext
from ...core.profile import Profile
from ...messaging.valid import DIDWeb

from ..base import (
    BaseDIDResolver,
    DIDNotFound,
    ResolverError,
    ResolverType,
)

[dbluhm]

This method should no longer be required, technically.

[swcurran]

I was trying this out and have found that while did:web:did.actor:alice resolves properly (e.g. matches more or less what the DIF Resolver returns. However, the other actors DIDs (e.g. mike -- did:web:did.actor:mike, URL: https://did.actor/mike/did.json ) does not resolve successfully. For Mike, the error is:

Error: Response was incorrectly formatted. Failed to deserialize DIDDocumentRoot:. 1 validation error for ParsingModel[DIDDocumentRoot]. __root__ -> @context -> 1. str type expected (type=type_error.str). [ErrorWrapper(exc=ValidationError(model='DIDDocumentRoot', errors=[{'loc': ('@context', 1), 'msg': 'str type expected', 'type': 'type_error.str'}]), loc=('__root__',))].

I'm guessing this is because of the JSON-LD contexts in the Mike document (and Carol). Is that the issue?

Thanks

[dbluhm]

PyDID is complaining about the embedded object in the @context which isn't strictly spec conforming. At this point, I'm seriously questioning whether we'll ever be able to expect DID Documents to be even mostly spec compliant lol... I thought I had loosened expectations around parsed DID Documents in use by ACA-Py though. Was this error raised while just querying the plugged in resolvers through /resolver/resolve/{did} or another operation?

[swcurran]

Yes -- I was using /resolver/resolve/{did}