`web3call` provider validation on start

Do you want to request a feature or report a bug?
bug

What is the current behavior?
When provider of type web3call specified, graph-node doesn't validate it on start. So you can specify any non-existing URL and graph node will not notice it until the first eth_call call.

I guess the issue is that EthereumNetworks::flatten() method that's used for provider validation, omits call_only_adapters field

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.
Add a provider with non-existing url:
{ label = "calls", details = { type = "web3call", url = "http://asdf", features = [ "archive" ] }},

What is the expected behavior?
Should drop that provider on start.

Commencez dans chain/ethereum/src/network.rs, en particulier dans EthereumNetworks::flatten(), et examinez la manière dont les call_only_adapters sont traités lors de la validation du provider. Reproduisez le problème avec un provider web3call utilisant l’URL inexistante http://asdf et confirmez qu’un provider invalide est supprimé au démarrage plutôt qu’au premier eth_call.