Narrative Overhaul: enskit migration from @ensnode/ensnode-react

[shrugs]

Broken out from #1793.

enskit has been scaffolded with enskit/react and enskit/react/omnigraph subpath exports (#1867). Complete the migration from @ensnode/ensnode-react: port remaining hooks/providers into enskit/react, update dependents, and remove the legacy package.

From #1793:

enskit — framework-specific wrappers of enssdk (unscoped npm package)

• enskit/react — React hooks and components wrapping enssdk
• enskit/react/omnigraph — opinionated urql-based Omnigraph client with logical defaults
• room for enskit/svelte, etc. in the future

Breaking changes are acceptable — no transition period required.

[coderabbitai]

🔗 Related PRs

#1636 - refactor(ensnode-sdk): move ENSNodeClient into ENSApi module [merged]
#1730 - Remove Core Plugin Restriction [merged]
#1758 - fix: allow ensv2 apis to be used without ensv2 datasource [merged]
#1832 - Fix ENSDb SDK builder for "concrete" ENSIndexer Schema [merged]
#1863 - chore(ensnode-react): Housekeeping refactors [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!