kirahsapong

Results 4 issues of kirahsapong

Also look at including previously resolved DIDs where we don't have access to the private key material. Will need a way to pass a filter like `ownsKey`

enhancement
did

`paymentDetails` is marked as optional within the `PrivatePaymentDetail` object, which is also optional in `privateData`. **Proposal:** `paymentDetails` should be required. ie. If passing the optional `PrivatePaymentDetail`, it _must_ contain `paymentDetails`....

Cross-fetch introduces deprecated dependency `punycode`, but we can address by removing the dependency altogether in favour of native node fetch. If maintainers agree I can push a PR.

stale

From @AlexHsieh in [this comment](https://github.com/TBD54566975/web5-swift/pull/55#issuecomment-2079413931): > Also at reading web5-js, found out that this line > > [`contentMetadata : didResolutionMetadata`](https://github.com/TBD54566975/web5-js/blob/277a201ff2c6dca1433a34d9cd0ffff7c511fcca/packages/dids/src/resolver/universal-resolver.ts#L228) > > should be > > `contentMetadata : didDocumentMetadata` >...