update on node-oauth broke passport-windowslive

Hi Jared,

This is a quick fix that will use the [request](https://github.com/mikeal/request) module instead of node-oauth `get` method (https://github.com/ciaranj/node-oauth/blob/master/lib/oauth2.js#L173). The problem is that Windows Live will reject the request to the API if the access token is sent both as a header and the query string (see [this thread](http://social.msdn.microsoft.com/Forums/en-US/messengerconnect/thread/5c7c6271-c0fb-4b90-b6e2-a5a6250b3847)). This started to surface since node-oauth was bumped 4 days ago including this new change that was committed four months ago (https://github.com/ciaranj/node-oauth/commits/master)

I didn't check if the OAuth spec says something about sending the access token in both places. This was an issue for us in production, so we took the easiest and more decoupled route.