Add ability to create RPC service chain

We want to update the `fetch` middleware in `eth-json-rpc-middleware`
and the Infura middleware in `eth-json-rpc-infura` to automatically fail
over to alternate RPC endpoints when the desired endpoint is down. To do
this, we need a way to string together a collection of RPC services,
where the first service represents the primary endpoint, the second
service is failover for the first, the third service is a failover for
the second, etc. This composite object should conform to the same
interface as an RPC service so consumers do not have to care whether
they are working with a single endpoint or a chain of them.

Also expose `RpcService`, `RpcServiceChain`, and `AbstractRpcService`,
since this completes the work that we should need to do to these
packages in order to proceed to others.

packages/network-controller/CHANGELOG.md

@@ -7,6 +7,12 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+### Added
+
+- Add `RpcService` for requesting a JSON-RPC endpoint using the retry and circuit breaker patterns, optionally forwarding to a failover endpoint if down
+- Add `RpcServiceChain` for connecting primary and failover RPC endpoints together into a single RPC service-like thing
+- Add `AbstractRpcService`, the interface for all RPC services
+
 ### Changed
 
 - Bump `@metamask/base-controller` from `^7.0.0` to `^7.1.0` ([#5079](https://github.com/MetaMask/core/pull/5079))