Create DID resolution test suite

[peacekeeper]

The DID test suite has sections on DID resolution and DID URL deferencing, however those don't actually test live resolvers (since that was out-of-scope for the DID Core specification). The DID Resolution specification does define a concrete HTTP(S) binding as well as a concrete representation of a DID resolution result. Therefore, a DID Resolution test suite should be created to test those additional pieces of functionality.

The VC HTTP API test suite depends on DID Resolution to some degree, but there is interest in minimizing that component and move it to this work item here.

[OR13]

I support this proposal.

In particular I think it's important to standardize resolution and dereferencing over https.

Especially as they relate to Verifiable Credentials.

At one point a while ago, i wrote a script that consumed the universal resolver config and then resolved all the did documents and "consumed / produced" them as JSON-LD to detect errors.

I think we could probably do something similar here, and maybe even use the JSON Schema and SHACL associated with did core.

Another thing I have noticed is returning the didDocument, metadata in the response body vs didDocument as the response body. I assume we have the same issue for dereference (with or without meta) as the response body or in it.

The did core spec is flexbile here, but we can make recommendations that reduce complexity.