Avoid mutating the "abstract" ENSIndexer Schema definition.

[tk-o]

The goal is to have buildConcreteEnsIndexerSchema function from ENSDb to not have side effects. Each call of this function should produce a new "concrete" ENSIndexer Schema object. The "abstract" ENSIndexer Schema object, as defined by the sum of exports from packages/ensdb-sdk/src/ensindexer-abstract/index.ts file, should remain immutable.

[coderabbitai]

🔗 Related PRs

#1613 - feat(ensindexer): introduce Indexing Status Builder module [merged]
#1642 - refactor(ensnode-sdk): public config data model [merged]
#1660 - ENSDb data model [merged]
#1702 - ENSDb Writer Worker for ENSIndexer [merged]
#1778 - ENSDb SDK: group database schema objects [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]

Temporary hotfix created in PR:

• Fix ENSDb SDK builder for "concrete" ENSIndexer Schema #1832