Split config objects in ENSApi

[tk-o]

ENSApi should have more than one config object. There's an idea where ENSApi uses two config objects:

1. The env-based config built from env vars, available as a static import.
2. The ENSDb-based config (including ENSIndexer Public Config), derived from async ENSDb read, that is shared via middleware.

It's best to start with a design for the requested changes, as there might be important details that have not yet been discovered.

More details in thse threads:

• https://namehash.slack.com/archives/C086Z6FNBHN/p1773092154129949
• https://namehash.slack.com/archives/C086Z6FNBHN/p1774338589997209

[coderabbitai]

⚠️ Possible Duplicate Issue(s)

• ENSApi: Persist ENSIndexerPublicConfig to the database #1252

🔗 Related PRs

#1566 - feat: separate ensv2 datasources out more correctly [merged]
#1642 - refactor(ensnode-sdk): public config data model [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!