Avoid duplicate documentation where possible

[igamigo]

What should be done?

RIght now, there are currently 3 places (AFAIK) where documentation needs to be updated whenever features are added or modified:

• The client's README
• The client's docs (./docs)
• Miden-base docs/tutorials

Furthermore, some of the information related to using the client depends on other projects (such as the node). I think we could reduce the README to more concrete information about what the client can do and reference other docs for usage examples, command explanations, etc.

How should it be done?

Deduplicate information on this repo and reference external docs when needed..

When is this task done?

Whenever the repo holds as little duplicate information as possible.

Additional context

No response

[bobbinth]

think we could reduce the README to more concrete information about what the client can do and reference other docs for usage examples, command explanations, etc.

I agree. When we didn't have more comprehensive docs, the README had to be pretty heavy - but now I think we can reduce the content here quite a bit.

We should also figure out how to keep the tutorial here rather than in miden-base.

[mFragaBA]

closing as #262 got merged