support no-cache requests

[jbaxleyiii]

This PR seeks to support a new FetchPolicy called no-cache. Unlike network-only (which has a somewhat confusing name I admit), this policy bypasses reads AND writes when interacting with the client. So it can be used to "turn off caching" when needed. This applies to mutations as well which now support using FetchPolicy but only for this use case (will throw otherwise)

[apollo-cla]

	Warnings
⚠️	There are library changes, but not tests. That's OK as long as you're refactoring existing code

	Messages
📖	Please add your name and email to the AUTHORS file (optional)

Generated by 🚫 dangerJS

[dennislaupman]

if I add the "no-cache" de returning data is undefined:

export default graphql(HomeViewQuery, {
	options: () => ({ 
		variables: { type: 'dailycatch' }, 
	  	fetchPolicy: 'no-cache',  
	}) 
})(home);

[quentin-]

Should this be marked as a breaking change in the changelog?
Calling mutation with a fetchPolicy used to be ignored, but will now throw an error.

[jamesplease]

@jbaxleyiii if you're bored in quarantine I'm curious to know what you might choose to name these options (i.e. "network-only", which you described as confusing above) if you didn't need to think about backwards compatibility!