ENSv2: Domain/Resolver/Registration History

[shrugs]

I'm not entirely sure of the product requirements at the moment, so i'm deferring this until later, and those requirements are more concrete. but the manager app and the portal and perhaps other third-party apps will definitely want to display some sort of history for a name or history for a resolver or history for a registry, etc., etc., which needs to encode either
a) a highly specific concrete list of actual ens protocol events that have occurred or
b) a higher-level abstraction over those events to simply describe the changes that have occurred, and then uis can pull the protocol-specific values from the rpc as necessary, for example, like the actual data and then decode it into the specific events for the ui.

i've left a sketch of the drizzle schema in the feat/ensv2-history branch so we can look at that later. we definitely want to make it easy to paginate over all of these rather than doing a union. and what exactly we store is highly dependent on the ui requirements.

[coderabbitai]

⚠️ Possible Duplicate Issue(s)

• notes from Portal App Refactor #1667

---

📝 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!