Make breaking API changes to align with docs

When I was writing the docs, I decided to write them for the API I want, not the one I have 😛

So we should make some changes to the library itself to bring it up to date:

• Make ApolloClient a default export of the package
• Make the arguments to ApolloClient an object instead of positional
• Make sure ApolloClient#query doesn’t take a returnPartialResults option
• Add a few more functions to WatchedQueryHandle

@jbaxleyiii @johnthepink heads up, these are definitely breaking changes. Let me know if you disagree with any of them. You can see the docs for examples of how it would look: https://apollostack.gitbooks.io/apollo-client/content/

[jbaxleyiii]

Perhaps by default, we should just assume the server doesn’t support the Relay Node spec, and just check if we have all of the query results on the client.

@stubailo I think this sounds great

[stubailo]

Perhaps by default, we should just assume the server doesn’t support the Relay Node spec, and just check if we have all of the query results on the client. Then we can set forceFetch to false, and it will help a lot for stuff like navigating to a route you just visited.