Switch to external graphql-tag package

[stubailo]

Completes #312.
Fixes #223.

@abhiaiyer91, you might be interested.

This also makes the following unnecessary:
#188 #190 @jbaxleyiii

TODO:

• Update CHANGELOG.md with your change
• Make sure all of the significant new logic is covered by tests
• Rebase your changes on master so that they can be merged easily
• Make sure all tests and linter rules pass

[jbaxleyiii]

@stubailo do you think it is more efficient (weight wise) to send the parser, or the compiled documents to the client? Mainly for a larger app. I was thinking about writing a meteor build package to take .graphql files to make the importable and parse them but was unsure if it was a good move?

[stubailo]

@jbaxleyiii last time I talked to Lee Byron he was thinking it might actually be more efficient to send the parser, depending on how big your queries are. The query AST is potentially large, so just a small number of queries could end up pretty heavy was his thought.

We can also experiment right? I don't think this PR changes anything about that option being available.

[jbaxleyiii]

@stubailo I came to the same conclusion. 👍

[helfer]

I think the most efficient thing would be to just send the operationName, if that's possible.

[stubailo]

@helfer sure, but that's orthogonal to this question because we need to know the query on the client even if we don't send it.