Fix defaultOptions.watchQuery.fetchPolicy not being used by useQuery

[yasharzolmajdi]

This PR is intended to solve the issue of default options in client not setting the correct fetch policy in useQuery.

when user doesn't set a fetch policy option in useQuery, it is defaulted to cache-first before it attempts to use the default fetch policy that is set in by the client.

the fetch policy hierarchy currently is:

1. user define fetch policy as parameter in useQuery
2. default to cache-first in useQuery
   it completely ignores default fetch policy from the client

with this PR it will be:

1. user define fetch policy as parameter in useQuery
2. user define fetch policy as default value in client
3. default to cache-first in useQuery

fixes #9105
fixes #2555

[apollo-cla]

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

[matrinox]

@yasharzolmajdi Tested this locally and it fixed it for me. The defaultOptions is used on the react hooks from 3.0.1 but I think somewhere between then and 3.5.6 (the one I'm using right now) it stopped using the defaults.

[hwillson]

Thanks for this @yasharzolmajdi! If you could add a test(s) to help verify this works as expected (and to help avoid regressions in the future), that would be helpful.

[yasharzolmajdi]

Thanks for this @yasharzolmajdi! If you could add a test(s) to help verify this works as expected (and to help avoid regressions in the future), that would be helpful.

@hwillson Thanks, I have added a test which currently fails on the main branch but passes with my changes

[hwillson]

Thanks for the test @yasharzolmajdi - this looks great to me. @brainkim @benjamn any objections to merging?

[brainkim]

Thank you for this!

[benjamn]

LGTM, and I can confirm the test fails when the changes are reverted. Thanks @yasharzolmajdi!