Bug: All arguments are expected to be objects vs method params or objects

[zcstarr]

Currently Jade Signer doesn't support the expressive ness of the open-rpc document. All the Json-RPC API interfaces don't respect individual params to be serialized ( as far as I can tell).

Motivation: We want to provide a nice logical interface for devs to interact with jade signer, this means that for request like export_Account. The format should not be

export_Account( {address: "0xBEAD.."}, {chainID: 61}) but preferably
export_Account("0xBEAD",61); Where the client type annotations inform the developer what is what. Additionally we should still support the former interface where it makes sense

Acceptance Criteria:
Jade Signer accepts single variable arguments to rpc request, meaning it supports named params and positional params.