feat(http): allow custom http codes along with custom response text

[lowlighter]

Closes #664

As specified in the rfc2616 spec:

HTTP status codes are extensible. HTTP applications are not required to understand the meaning of all registered status codes, though such understanding is obviously desirable. However, applications MUST understand the class of any status code, as indicated by the first digit, and treat any unrecognized response as being equivalent to the x00 status code of that class, with the exception that an unrecognized response MUST NOT be cached. For example, if an unrecognized status code of 431 is received by the client, it can safely assume that there was something wrong with its request and treat the response as if it had received a 400 status code. In such cases, user agents SHOULD present to the user the entity returned with the response, since that entity is likely to include human- readable information which will explain the unusual status.

Since this PR allows custom codes which may have not default response text defined, this also add statusText so custom error codes can be sent with human readable messages.

[alexanderGalushka]

@bartlomieju can you please look at this PR

[kt3k]

LGTM