add support for non-GET methods

1) Should I add validation on method in the Request function? Or should I just let the API handle it/return an error there?
2) A note on the tests: I didn't want to try to mock out the whole API and making sure the responses were accurate for the new methods, but rather I wanted to test that the requests were being formatted and sent correctly. Since this library isn't dependent on the API actually making the changes to maintain state, it shouldn't be the responsibility of this library to make sure that the API is returning accurate responses. I'm open to pairing on tests if you think they should be done differently.
add support for non-GET methods

1) Should I add validation on method in the Request function? Or should I just let the API handle it/return an error there?
2) A note on the tests: I didn't want to try to mock out the whole API and making sure the responses were accurate for the new methods, but rather I wanted to test that the requests were being formatted and sent correctly. Since this library isn't dependent on the API actually making the changes to maintain state, it shouldn't be the responsibility of this library to make sure that the API is returning accurate responses. I'm open to pairing on tests if you think they should be done differently.
Merge branch 'support-other-methods-for-api-requests' of github.com:Clever/clever-go into support-other-methods-for-api-requests

Conflicts:
	clever_test.go
turn off debug
better function name
comment and error styles
add content-type json to header
add header test
Merge pull request #13 from Clever/support-other-methods-for-api-requests

Support other methods for api requests