Consider pruning and index depth

For some requests it critical to route a request to a node which have a response in it's index. It could be:

- for `eth_getTransaction*` to be in `--txlookuplimit` range
- for archive requests to be in `--prune` range

Note that Erigon has different type of pruning, for history, receipts, transaction and call traces. Though it may be configured through a combination of prune range and list of allowed methods.

TBD how to handle all of these ranges