Basic Framework #1
Description
Infra provider should be able to register a list of AntelopeIO rpc nodes to proxy requests to. The firewall should be able to listen to requests and distribute the requests to those nodes using configurable logic (like round robin, random, or least connected). The Firewall should use the rpc get_info endpoint to check the status of nodes and prevent routing requests to them if they are offline or out of sync. Nodes in the list should be able to be tagged as having available services for routing. (For example: some nodes may provide v1 or v2 history solutions in addition to standard rpc services, some nodes may only be used for queries while others are only used for pushing transactions). Maybe instead of tags it's implemented as multiple lists (all, v1, v2, read-only, push-only, read-push) etc... open to ideas here.
Firewall should be able to listen for requests on a configurable port. ( do we want to implement https support or do we assume most providers are already handling https higher up in their stack)
Configuration should be done via a config file with plans for an admin rpc later. It would be nice but not required, to be able to update the configuration without restarting the process.