dev: initial work on NameSystem, wrapping the underlying DHT network.

[jsantell]

Implementation of the NameSystem propagating records through the DHT network.

• Top-level exports like NameSystem, NameSystemBuilder and NSRecord all have rather robust tests and docs.
  • NSRecord is the struct being transmitted over the DHT. Rolling our own de/serializer due to cid's built-in serde implementation always writing to bytes. The structure is transmitted as JSON UTF-8. Flexible about details here, but is an area that will need to be "standardized" as part of the protocol. I imagine additional fields on here once we add UCAN.
  • NameSystem and NameSystemBuilder APIs are flexible, but attempt to mimic DNS.
  • Re-exports aren't ideal, but the multiformats Cid and Multiaddr are rather intrinsic to Noosphere/NS.
• ns_test is a good example of functionality.
• Very few interesting changes in the underlying dht implementation, mostly clippy/lint changes.
• Not yet implemented:
  • CLI demo; initial work stashed elsewhere for now, can integrate it fully into orb when ready
  • SphereIpld integration; initial work stashed elsewhere containing a names entry, can start this either with UCAN or CLI integration.
  • Any UCAN integration (hydration, validation)
  • Automatically propagating provided records at TTL interval

[cdata]

This is a really crisp iteration over what has already been landed, great work! I have some general questions and a few small actionable items, but otherwise I'm happy for us to ship it.

[jsantell]

Updated with UCAN integration, where records are authorized and set as UCAN tokens, and propagated on the network in their encoded form. Previous comments have been addressed; I'll inline the areas of interest from previous review -- NSRecord and ns_test are the majority of changes

[cdata]

I don't have any feedback for changes, just some questions. This looks like really great progress, and we can land it when you are ready.

[cdata]

Great work as usual 🙌