Preconf RPC Improvements: Generalize Considered Provider Set #730
Description
The RPC currently issues a preconf is commitments from all providers that have a node on the network are received. This means that if a provider is registered but does not run a provider, the RPC still issues preconfs without this provider committing, even though the provider could build a block. This is fine for the wallet RPC use-case, but problematic for instant bridging since funds could get lost in this case.
Ideally, the RPC could be configured to look at different sets for different use cases. E.g., for bridging, one may want to get a commitment from all providers that are registered (even if they don't run a node and would never commit). For other use cases, getting commitments from all "big" providers may be sufficient.