Refactor code for readability and maintenance about memstate HOT 2 CLOSED

This issue exists as a reminder.

I suggest that we rename MemstateServer and MemstateClient to TcpServer and TcpClient. TcpClient is more specific and follows the same naming as LocalClient. This allows us to add HttpClient, UdpClient, etc. in the future without having a weird naming scheme.

For MemstateServer, I suggest either TcpServer or dropping the Tcp prefix and calling it Server.

from memstate.

I considered TcpServer and TcpClient as these are the most natural names but decided not to use them to avoid confusion with the dotnet framework types in System.Net. I agree that MemstateServer and MemstateClient are poor names but TcpServer and TcpClient are not great either.

Also, there will most likely only be a single transport (tcp) for commands and queries. If we add an http transport, then perhaps just use the default HttpClient?

Alternatively, we could set the transport as a setting:

var settings = new MemstateClientSettings();
settings.Transport = Transport.Tcp;
var client = await Client.ConnectAsync(settings);

from memstate.