Make ENSDb Client to use its own schema

[tk-o]

We need ENSDb Client to work with its own database schema. The database schema will, at least initially, include metadata table managed 100% by ENSDb Writer Worker from ENSIndexer, and other ENSDb clients will be able to read from that table using ENSDb Client (backend) package.

Related proof of concept: #1714

---

Starting with PR #1702, ENSDb Client implementation for ENSIndexer performs updates on ENSDb. However, the ENSDb Client uses a database schema that is managed by Ponder runtime. After talking to the team, we figured that ENSDb Client needs to use its own schema, entriely isolated from Ponder schemas.

[coderabbitai]

🔗 Related PRs

#1711 - Fix writes through ENSDb Client [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!

[tk-o]

Completed with #1798