`enssdk` — Migrate core types and utilities

[shrugs]

• export the various Label and NameandLiteral*andInterpreted*types and associated helpers fromenssdk`
• export namehash and labelhash utilities
  • goal: consumers don't need to import from viem
• re-export the viem Address and Hex types
  • adjust all imports in the ensnode monorepo to use the enssdk-exported types instead of importing from viem
  • perhaps viem needs to be moved from a peer dep to a dep? otherwise all consumers will need to also add viem to their deps. but if we make it a dep and apps also want to access viem (common) they'd perhaps have to juggle versions
• consider moving constants like ADDR_REVERSE_NODE and ROOT_NODE?
• TokenId as well
• packages/ensnode-sdk/src/ens/names.ts

[coderabbitai]

🔗 Related PRs

#1566 - feat: separate ensv2 datasources out more correctly [merged]
#1636 - refactor(ensnode-sdk): move ENSNodeClient into ENSApi module [merged]
#1660 - ENSDb data model [merged]
#1778 - ENSDb SDK: group database schema objects [merged]
#1857 - Omnigraph Refactor (cont) [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!