consistent and descriptive json-rpc error codes and messages

[dinhani-cw]

Currently there is not a clear approach of how to respond clients when there is an error, expected or unexpected.

In some cases we provide a custom message, but in other scenarios we pop-up the internal error message.

We should map all possible error responses to a Rust enum and use it as the source of error responses.

[marcospb19-cw]

to close this one it's necessary to review errors are raised with anyhow::Error instead of StratusError
https://github.com/search?q=repo%3Acloudwalk%2Fstratus+anyhow%3A%3AResult&type=code
with that, you can spot any unmapped errors