Hello there, thank you for the awesome work.

I'm looking for a solution for two issues I faced with twitter-rest.

1. when the request fails, a generic exception is thrown. The message of the exception is mixed with the JSON data of the response. This means you don't get programmatic access to the error code that comes in the JSON data. You also don't get access to the HTTP error code.
2. in non trivial applications, you need to check your rate limits. One way to do it, is to check the headers of the twitter response. But you don't get access to them either.

Possible solutions:

• create a way to get a raw response object, which contains the parsed json data, the headers, etc. It may be a different method, or a optional parameter in Twitter::send(). Ideally, an exception should never be thrown when using this method/parameter.
• create a specialized exception (let's say TwitterException) with a getResponse() accessor and perhaps some more specialized method. This wouldn't solve the point 2 though, which is of critical importance.

Let me know what you think.

The first aim of this PR is to introduce request options in order to avoid duplication in all requests.

Additionally, the request does not inherit any class anymore in order to avoid method collision due to the usage of the magic method.

For the moment, it is much more a POC than something else. so, if you agree, then threre is still some tests which need to be written before considering the PR to be merged.

ping @geoffrey-brier @tmartin