Check is_stable per chain not just NEAR network

[ChaoticTempest]

Since we have ETH indexing now, we should check the stability of eth alongside NEAR as well.

The main point of attention would be when and where to publish a signature based on the chain. So when a new request is received by SignatureManager we should sort the stable participants based on chain and their equivalent indexer is_stable condition.

Right now, we publish StateView::Running { is_stable, .. } where is_stable is from NEAR network. We need a way to add in eth as well. Maybe something like this additional field would suffice:

StateView::{Running, Resharing} {
   chains: Map<Chain, ChainInfo>
}

struct ChainInfo {
    latest_block_height: u64,
    is_stable: bool,
    // other chain related info
    ..
}

And then when we go to organize our requests, we can then utilize this info for better handling

[volovyks]

We will have many more chains soon. I'm not sure if adding additional parameters to the structure is the best idea, but I agree that we need to distinguish them.

[ChaoticTempest]

how else would we distinguish stable participants then? We need a way to provide this info somehow