Clarify the ERPpeek -> Odooly fork

[mbello]

Today I went to the ERPpeek github and saw the fork notice pointing to Odooly.

For people coming in for the first time I believe it is important to add on your documentation or README an explanation of why/how the fork happened and try to explain why people should use Odooly instead of ERPpeek now.

We have 3 options right now (Odooly, OdooRPC and ERPpeek), you should address this directly to help people choose.

Sorry to make this an issue, consider this a documentation issue maybe.

[florentx]

You're right, I need to add this to the documentation.

In short, the benefit is to have a more consistent API, which is the same as Odoo internal API.
(ERPpeek was developped before the new Odoo API v8 was released)

For example the browse(domain_or_ids) of ERPpeek could be confusing because it covered both search(domain) and browse(ids) of Odoo API v8.
Other enhancements are all the features of Odoo internal API v8 (+ usage of the more powerful RPC method execute_kw instead of execute).