Wallet API Structure

[yeastplume]

Goal of this one is to try to build out a skeletal framework of the entire wallet API structure a bit, with all of the parts in place to handle both local (command line) functionality as well as a localhost-only rest API.

The API is to be split into internal (owner functions) and external (communication with other people) functions (in fact I'll probably rename then as such,) and a framework in place to allow a caller to instantiate them in whatever means is desired, for instance:

• A command line client wanting to call owner functions should get a single-use owner version of the wallet API, which will instantiate with given params, call whatever api functions are needed, clean up and return
• A web API listener implementation should be able to invoke the exact same interface as a listener, with all of the API functions neatly wrapped as json calls.

Still experimental, so I'll fill in more details as I go along and figure out how all of this should be structured.