Consider trying to load `@apollo/client/core` in node.js

```bash
node -v # 16.3.0
```
```js
// server/index.js
import { ApolloClient } from '@apollo/client/core';
```
> import { ApolloClient, InMemoryCache } from '@apollo/client/core/index.js';
>          ^^^^^^^^^^^^
> SyntaxError: Named export 'ApolloClient' not found. The requested module '@apollo/client/core/index.js' is a CommonJS module, which may not support all module.exports as named exports.
> CommonJS modules can always be imported via the default export, for example using:

```js
import AC from '@apollo/client/core';
const { ApolloClient } = AC;
```
> (node:35704) Warning: To load an ES module, set "type": "module" in the package.json or use the .mjs extension.
> (Use `node --trace-warnings ...` to show where the warning was created)
> /path/to/node_modules/@apollo/client/core/index.js:1
> export { ApolloClient, mergeOptions, } from "./ApolloClient.js";
> ^^^^^^
>
> SyntaxError: Unexpected token 'export'

adding `"type": "module"` to core will solve those errors nicely

For example, this rewrites the import from "ts-invariant/process" in
@apollo/client/utilities/globals/graphql.js to instead import from
"ts-invariant/process/index.js, so Node.js won't complain about the
directory import (even though ts-invariant/process/package.json exists).

Add `"type": "module"` to `@apollo/client/**/package.json` (all entry points).

And so it begins again. 😅

May help with #8557.

This will allow us to release the changes from PR #8558 in a beta
release before merging them to main and publishing v3.4.1.

The root package.json file was neglected in #8396, since it isn't
generated in the same way as the other (nested) package.json files.

This commit puts `"type": "module"` in the _published_
`@apollo/client/package.json` file, which is generated at build time as
the file `dist/package.json`. The root `package.json` file that's
checked into the repository does _not_ contain `"type": "module"` (even
though putting it there would also put it in `dist/package.json`).
Attempting to enable ES module syntax at that level interfered pretty
severely with tools like ts-node, which we use to run various
config/*.ts scripts. Rewriting those scripts is a job for another time.

I'm happy to revisit this as the ecosystem progresses.

After #8414, the
changes made in #6107
are unnneccessary, because all ObservableQuery callbacks will only be
fired in useEffect calls (hopefully). This changes the timings of some
of tests.

Preparing to refactor QueryData away by trying to simplify some of its
logic and inlining a majority of its methods.

I honestly have no idea what these partialRefetch tests are testing but the one test we’ve written for it now passes

update the getObservableQueries thingy to use `all` because apparently that’s a thing

…aseQuery, useDeepMemo, useFastRefresh

The Lannisters send their regards

Fixes #5140

Fixes #7564

Confirms #5531 is fixed.

Fixes #8270

…te is called multiple times

Fixes #7396

…mpleted

React refactorings

This merge of the still-open PR #8689 into `release-3.5` will allow us
to test those changes in an `@apollo/client@beta` release before merging
to `main` and releasing in v3.4.x.

…pes/zen-observable` (#8695)

Includes apollographql/zen-observable-ts#152

Should fix #8688

Co-authored-by: Ben Newman <ben@apollographql.com>