Make Ponder Build ID unique when any value in indexing behavior dependencies change

[tk-o]

From a Slack thread:

I found out that Ponder, since version 0.11.40, has been ignoring most of the fields of the object exported from ponder.config.ts file. The breaking change was introduced here. This means that the indexingBehaviourDependencies field has been ignored for a while now. What’s more, I learnt that the Ponder Build ID is generated based on the literal contents of ponder.schema.ts file. It means, that even if we change ENSIndexer Schema in ENSDb SDK, the ponder.schema.ts file content remains unchanged, so does the Ponder Build ID.

[coderabbitai]

🔗 Related PRs

#1612 - Apply specific variant types for ChainIndexingMetrics [merged]
#1613 - feat(ensindexer): introduce Indexing Status Builder module [merged]
#1726 - deps: update ponder to latest patch [merged]
#1778 - ENSDb SDK: group database schema objects [merged]
#1807 - Skip ENSDb Writer Worker validation for ENSIndexer Public Config while in dev mode [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]

Resolved with #1913