Fix issue where changes to @export fields did not trigger updates (#13367)

Fixes #13335

We had a regression in 4.x with regards to `@export` fields where
queries would sometimes not respond to cache updates. This happened when
a field changed an object that depended on the variables keyed by the
`@export` values.

```gql
query ($userId: ID!) {
  userId @client @export(as: "userId")
  user(id: $userId) {
    id
    name
  }
}
```

In this case, `ObservableQuery` subscribed to the cache using the
initial empty variables value, but never resubscribed after export
variables were known. This meant changes to data inside that `user`
object never notified the query of the change.

This fix now emits a `resolvedVariables` value along with the
notification to `ObservableQuery` so that `ObservableQuery` can update
its `variables` and resubscribe to the cache using the export variables.
I added a whole bunch of other tests to catch other potential edge cases
to make sure we didn't miss this for other situations.

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

* **Bug Fixes**
* Fixed reactivity issues affecting queries that use `@export`
variables.
* Cache updates now correctly trigger refreshed results when
exported-variable fields change or are evicted.
* Improved behavior for refetching, partial data, cache-and-network
requests, and network-only requests.
* Improved handling of streamed responses and variable changes during
in-flight requests.

* **Tests**
* Added coverage for cache, network, refetch, partial-result, and
streaming scenarios involving `@export` variables.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Co-authored-by: jerelmiller <565661+jerelmiller@users.noreply.github.com>

Author: jerelmiller

.api-reports/api-report-core.api.md

@@ -1116,10 +1116,12 @@ interface QueryManagerOptions {
 namespace QueryNotification {
     // (undocumented)
     type FromCache<TData> = NextNotification<ObservableQuery.Result<TData>> & {
+        resolvedVariables?: OperationVariables;
         source: "cache";
     };
     // (undocumented)
     type FromNetwork<TData> = ObservableNotification<ObservableQuery.Result<TData>> & {
+        resolvedVariables?: OperationVariables;
         source: "network";
     };
     // (undocumented)

.api-reports/api-report.api.md

@@ -2530,10 +2530,12 @@ interface QueryManagerOptions {
 namespace QueryNotification {
     // (undocumented)
     type FromCache<TData> = NextNotification<ObservableQuery.Result<TData>> & {
+        resolvedVariables?: OperationVariables;
         source: "cache";
     };
     // (undocumented)
     type FromNetwork<TData> = ObservableNotification<ObservableQuery.Result<TData>> & {
+        resolvedVariables?: OperationVariables;
         source: "network";
     };
     // (undocumented)

.changeset/stale-moles-tap.md

@@ -0,0 +1,5 @@
+---
+"@apollo/client": patch
+---
+
+Fix an issue where some `@export` queries would not react to cache updates when the fields keyed by exported variables were updated.

.size-limits.json

@@ -1,6 +1,6 @@
 {
-  "import { ApolloClient, InMemoryCache, HttpLink } from \"@apollo/client\" (CJS)": 47972,
-  "import { ApolloClient, InMemoryCache, HttpLink } from \"@apollo/client\" (production) (CJS)": 42227,
-  "import { ApolloClient, InMemoryCache, HttpLink } from \"@apollo/client\"": 35919,
-  "import { ApolloClient, InMemoryCache, HttpLink } from \"@apollo/client\" (production)": 29427
+  "import { ApolloClient, InMemoryCache, HttpLink } from \"@apollo/client\" (CJS)": 48044,
+  "import { ApolloClient, InMemoryCache, HttpLink } from \"@apollo/client\" (production) (CJS)": 42315,
+  "import { ApolloClient, InMemoryCache, HttpLink } from \"@apollo/client\"": 35982,
+  "import { ApolloClient, InMemoryCache, HttpLink } from \"@apollo/client\" (production)": 29489
 }