Need to identify and forbid very expensive queries

[proehlen]

Searching reveals no standard way to implement this and various teams/products have used different approaches.

Suggest we use the context argument to track the query as it is executing and generate an error when the cost becomes too high. Metrics that could be tracked include:

• Depth
• Number of resolver hits
• Cumulative size of data returned by resolvers