Add standardization to HTTP response

[zeeshanbhati]

• Standardization of HTTP Response
  If this gets merged, the doc and frontend need to be updated

[lucifercr07]

@zeeshanbhati please resolve the conflicts.
If we're going to standardise we shall try to find a way to differentiate between API request related errors and internal server errors and communicate them properly.
e.g. If a command is executed via API like GET k1 and k1 doesn't exists then it's an error from DB as nil which is valid and should be propogated as it is to client/UI.
If the API request is failed to parse or some panic occurs due to DB disconnect etc. we should wrap that error properly and convey differently so that UI can differentiate and give a generic response.

Please let me know your thoughts around this.

[zeeshanbhati]

@lucifercr07 do we want to send the error as it is or do we need to add something or modify it that should be handled on the service layer, But that really does not change the format of the response added into this PR. unless you are getting gateway timed-out errors or your API is unreachable it should give a standard format response like

{
data: object or string,
error : Object or string,
hasData: boolean,
hasError: boolean,
}

An example could explain it better!

Please let me know what you think about this.