Change how config value is used in lib functions

[tk-o]

Files under apps/ensindexer/src/lib/* path should not directly import config from @/config. Instead, functions in those file should require relevant config slice (i.e. Pick<ENSIndexerConfig, "ensDeploymentChain" | "plugins">) from the application-level caller.

Application level caller might be located in: a handlers file, ponder.config.ts file, ponder.schema.ts file. In short, all files which ponder uses as its entrypoints.

[tk-o]

Please note, that removing @/config dependency can be tricky for type inference (expect typescript issues).

[lightwalker-eth]

Thanks for recording this.

As I understand the key goal here is to be more cautious with circular dependencies, even if technically they work, conceptionally they seem a bit dangerous or prone to future issues.

Let's see what happens after we complete the work on pushing our config strategy forward all the way through ENSAdmin. After we finish that I think we'll have a better opportunity to see what the next steps on this might be.

[tk-o]

The type inference issues are to be expected on the ENSIndexer end, as we use createConfig function from ponder package that requires literal input values. If we can make our config builder process to stop working on inferred types and use cost types instead, we should achieve type inference stability.

In other words, we need to play ponder's const generic types game for during our config build process, so at the end we can pass a const-typed value into createConfig from ponder:

https://github.com/ponder-sh/ponder/blob/a069bd8d984a8958df81c6d0249423d91483fda0/packages/core/src/config/index.ts#L28-L41