Cancel queryInfo.notifyTimeout when marking final results.

[benjamn]

As the reproduction in #7346 demonstrates, it was possible for the QueryInfo#notify timeout set in QueryInfo#setDiff on behalf of an earlier loading: true result to fire after the final loading: false result had been recorded in QueryInfo#markResult, which could lead to unnecessary network requests when using a FetchPolicy of cache-and-network or network-only, especially when there are multiple useQuery calls in the same React component.

This PR fixes that problem by canceling the timeout in QueryInfo#markResult and markError, since those methods are called by code that delivers the results through other mechanisms.

[hwillson]

Looks great @benjamn - thanks!