Allow for storing and displaying responses

[nextrevision]

Optionally allow for storing and displaying response data like headers and content. I'm using this with the response proxy. Not sure if you want to support something like this, but if so, I can polish up my fork and submit a PR.

[darklynx]

This make sense if combined with issue #24, there is already a structure to hold the Response defined in the API. The Request may optionally contain a response property then.

Probably another boolean flag to enable storing the responses would make sense in the settings, or it should be implicitly enabled, when basket operates in "full proxy" mode, and disabled otherwise.

I'm open to discuss the options here :)

[nextrevision]

I'll add the boolean flag, since storing the responses can run up the memory when using the in-memory store. I currently have the response nested in a request struct, but will play around with the data structure.

[darklynx]

I guess its fine to encapsulate response in request, otherwise the API break should take place: I mean the external REST API

[DustRaven]

What about this? Can we already do this, or is this still under consideration?