0.3 breaking changes

[dkackman]

In order to make it possible to use the same proxy class to communicate to an endpoint via the daemon or directly I needed to refactor some things; mostly in how the daemon is used.

• Their are now 2 rpc client implementations, one that uses websockets (for the daemon) and another for https (for the direct rpc service endpoints)
• The daemon no longer derives from RpcClient, but rather inherits from ServiceProxy like everything else. (and is renamed DaemonProxy).
• It will now be possible to talk directly to the harvester, farmer, full node or wallet without the daemon. The motivation for this is to support remote management use cases where you don't want to expose the entire daemon interface to the network.
• The ServiceProxy derived classes can be used to talk via the daemon or direct, so there should be no code changes other than in setup
• Unrelated to the above, but BigInteger will be replaced with ulong wherever possible.

Connecting

Before

var endpoint = Config.Open().GetEndpoint("daemon");
using var daemon = new Daemon(endpoint, "unit_tests");

await daemon.Connect();
await daemon.Register();

var fullNode = new FullNodeProxy(daemon);
var state = await fullNode.GetBlockchainState();

After

var endpoint = Config.Open().GetEndpoint("daemon");
using var rpcClient = new WebSocketRpcClient(endpoint);
await rpcClient.Connect();

var daemon = new DaemonProxy(rpcClient, "unit_tests");
await daemon.RegisterService();

var fullNode = new FullNodeProxy(rpcClient, "unit_tests");
var state = await fullNode.GetBlockchainState(e);

Direct

var endpoint = Config.Open().GetEndpoint("full_node");
using var rpcClient = new HttpRpcClient(endpoint);

// no need for connect or register

var fullNode = new FullNodeProxy(rpcClient, "unit_tests");
var state = await fullNode.GetBlockchainState(e);