Refine use of terminology between useENSNodeConfig and useENSIndexerConfig

[lightwalker-eth]

I'm currently reviewing apps/ensadmin/src/components/ensindexer/hooks.ts in PR 919.

Here a new hook is proposed: useENSIndexerConfig. It would be better if this hook could be called useENSNodeConfig. However, we already have a useENSNodeConfig hook. Therefore, suggest we investigate options for renaming the existing useENSNodeConfig hook.

[tk-o]

@notrab your support here would be much appreciated. Please advise on how we should rename the useENSNodeConfig hook?

[tk-o]

I'm planning to rename useENSNodeConfig hook to useENSNodeOptions, and ENSNodeConfig type to ENSNodeOptions.

The goal is to express ENSNode options available in the ensnode-react package. These options include just the client prop at the moment.

Another option would be to flatten useENSNodeOptions to be just about the client. For example, useENSNodeClientOptions() hook would return ENSNodeClientOptions type.

[notrab]

@tk-o sounds good to me!

[lightwalker-eth]

With the introduction of ENSApi, now ENSApi should be returning its own config object that has an ENSIndexer object nested within it. Can we please review the terminology for these data models and for the React hooks associated with these APIs?