Add generic error response to tcp protocol

Created by: davecromberge

This PR proposes a generic error response to a TCP command.

I could not run the eqc tests due to licensing limitations.

Since the client synchronously awaits a reply in response to a command, including the original command in the error message seemed unnecessary. I would like to know your opinion on adding a term to the error that matches the atom used in the original command, e.g:

{error, stream, <<"A bucket already exists with a different resolution">>} vs {error, <<"A bucket already exists with a different resolution">>}