Refactoring of client code into a library

[bramvdbogaerde]

This pull request tracks the progress on refactoring the Innernet client side (see issue #126).

It proposes the following changes:

• Rename the client crate to the cli create to make the distinction between multiple frontend clearer
• Create a client library crate which will host the code shared between frontends
•  Move the API calls into the client library
•  Move common code (such as the loop that periodically updates peers, adding peers, ...) into the client library
•  Create a Store crate which can be used to keep track of Innernet's local state in a platform and frontend agnostic way, the sole implementation of this trait will initially be the already implemented file backed store

These are the initial proposed set of changes, it should make it easier to extend Innernet with more interaction surfaces that can be decoupled from the main Innernet codebase.

Comments and feedback are greatly appreciated.

[mcginty]

Thanks for kicking this off! I think this is the right way forward, including breaking up the client into a couple of logically separated crates (and moving some of the current workspace crates out into their own repositories and putting them on crates.io).

Looks good so far. How can I help?

[mcginty]

I'm going to go ahead and close this until there's an active effort. Thanks for getting the conversation started @bramvdbogaerde!

[bramvdbogaerde]

Indeed, I didn't have the time to progress this much further. I might reopen it in the future.