Update did:dht to conform to the latest version of the specification

[decentralgabe]

There have been a number of changes to the DID DHT spec since implementation, which I've captured below. These changes should be backwards compatible, meaning DIDs you use today will not break.

These changes are already in place in the DID DHT project itself, and you can find passing test vectors here as a reference.

1. Support the three test vectors listed here: https://did-dht.com/#test-vectors
2. Support NS records to be set to the publishing gateway (as per https://did-dht.com/#designating-authoritative-gateways, Consider adding NS records to point to gateways did-dht#129)
3. Always set alg and kid on expansion (to the values in the registry), support overriding of alg values (as per Update spec to include language on default verification relationships, guidance on the alg property did-dht#148)
4. Support TXT records over 255 characters (as per Address TXT records > 255 characters; make language more consistent; separate section for root records did-dht#162)
5. Set verification method's controller property, allow overriding (as per add version number and controller property did-dht#102)
6. Stamp version field in the root record - set to 0 for now (as per add version number and controller property did-dht#102)
7. Support multiple service endpoints (as per Multiple spec changes - support for aka, controller, ; -> , & list of service endpoints did-dht#86)
8. Support X25519 (as per Update spec to include language on default verification relationships, guidance on the alg property did-dht#148) - note this is required for the 3rd test vector

Additionally, I would recommend:

9. Support a republish feature, which is able to take the latest state of a DID DHT document and re-publish it to a gateway.

If not in practice already, it would make sense to expand our "PortableDID" construct to store histories of DID DHT documents and republish should only work on the latest version (seq num).

---

After this you can anticipate two additional changes to DID DHT pertaining to the following issues:

• Provide a way to specify how long a retention proof retains  did-dht#74
• Add guidance for rotating to a new DID did-dht#100

74 will be a breaking change, though (9) from above paves a path to make it less disruptive.

Please let me know if you have any questions.