Add cache-and-network to FetchPolicy options

[greggb]

cache-and-network is a valid choice for fetchPolicy, and while it is documented, it is not part of the QueryOptions interface.

[benjamn]

This was an intentional change in Apollo Client 2.6.0, discussed in #3130, and documented in CHANGELOG.md:

• The FetchPolicy type has been split into two types, so that passing cache-and-network to ApolloClient#query is now forbidden at the type level, whereas previously it was forbidden by a runtime invariant assertion:

  export type FetchPolicy =
    | 'cache-first'
    | 'network-only'
    | 'cache-only'
    | 'no-cache'
    | 'standby';
  
  export type WatchQueryFetchPolicy =
    | FetchPolicy
    | 'cache-and-network';

  The exception thrown if you ignore the type error has also been improved to explain the motivation behind this restriction.
  
  Issue #3130 (comment) and commit cf069bc7

[benjamn]

If you're using React Apollo, you may want to update to [email protected] (published this morning).

[apollo-cla]

@greggb: Thank you for submitting a pull request! Before we can merge it, you'll need to sign the Meteor Contributor Agreement here: https://contribute.meteor.com/

[greggb]

If you're using React Apollo, you may want to update to [email protected] (published this morning).

Funny, this works just fine (using react-apollo-hooks), it's just the type def that shows an error. Thanks for pointing me to the correct thread.