Adds new field: resolver_urls to RpcConfig which allows specification of custom resolver urls
If no resolver urls are specified, default resolver is used.
In the current implementation if a random node is offline, KNG will stall which hurts user experience. The addition of Resolver ensures that the user is always connected to an online node.
When selecting a custom server from a predefined list, the current implementation uses a hardcoded list. This is bad from a maintainability standpoint which is why this PR queries all resolvers on their /status endpoint which returns a list of active nodes. This ensures that the user will always be able to select nodes that are filtered based on their online status.
Resolver.resolver_urlstoRpcConfigwhich allows specification of custom resolver urlsResolverensures that the user is always connected to an online node./statusendpoint which returns a list of active nodes. This ensures that the user will always be able to select nodes that are filtered based on their online status.