Allow custom JSON flavors for "client" code

[arnetheduck]

#238 changes the encoding of JrpcConv to suite the constraints of nim-web3 in particular.

However, other RPC protocols might want to encode their JSON in a different Flavor - thus, one should be able to customize which Flavor is used to encode a specific client/server, rather than always using JrpcConv.