Consolidate ideas around building ENSDb Config into ENSDb SDK

[tk-o]

Original request was posted here.

We want the ensdb-sdk package to be useful for everyone building on ENSDb.

Therefore the ideas such as the following should be moved into ensdb-sdk:

• DatabaseUrlSchema
• EnsIndexerSchemaNameSchema
• EnsDbConfigSchema
• EnsDbConfig

Then, we could also move buildEnsDbConfigFromEnvironment to ensdb-sdk but the function signature would need to be better generalized so that it just took the database url and ensindexerschemaname as string params.

The call to buildEnsDbConfigFromEnvironment in apps/ensapi/src/config/ensdb-config.ts could then be easily updated to match the new signature.

Before addressing this issue, let's have the following issues resolved:

• Replace databaseSchema term with a more precise one #1762
• Replace databaseUrl with ensDbUrl #1763

[coderabbitai]

🔗 Related PRs

#1630 - refactor(ensnode-sdk) Duration schema [merged]
#1636 - refactor(ensnode-sdk): move ENSNodeClient into ENSApi module [merged]
#1660 - ENSDb data model [merged]
#1772 - Rename @ensnode/ensnode-schema to @ensnode/ensdb-sdk [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!