…ndScheduleNext() is suspended would still result in setTimeout() being called. (#5222)

…5179)

Part of #5157.

The `apollo-server-testing` package exports one small function which is
just a tiny wrapper around `server.executeOperation`. The one main
advantage it provides is that you can pass in operations as ASTs rather
than only as strings.

This extra layer doesn't add much value but does require us to update
things in two places (which cross a package barrier and thus can be
installed at skewed versions). So for example when adding the second
argument to `executeOperation` in #4166 I did not bother to add it to
`apollo-server-testing` too. We've also found that users have been
confused by the `createTestClient` API (eg #5111) and that some linters
get confused by the unbound methods it returns (#4724).

So the simplest thing is to just teach people how to use the real
`ApolloServer` method instead of an unrelated API.

This PR allows you to pass an AST to `server.executeOperation` (just
like with the `apollo-server-testing` API), and changes the docs to
recommend `executeOperation` instead of `apollo-server-testing`. It also
makes some other suggestions about how to test Apollo Server code in a
more end-to-end fashion, and adds some basic tests for
`executeOperation`.

Fixes #4952.

If you use direnv and/or nvm, this helps synchronize the version of Node
you're running in the repo. (Especially helpful right now when flipping
back and forth between main and release-3.0.)

If this causes problems (eg, you do like using direnv but you don't like
this particular way of setting it up) we can make it more configurable.

Apollo Server shouldn't need to have deep knowledge of Apollo Studio's
data model. "ID and variant" are overly precise. This PR moves us
towards a world where Apollo Server only needs to be aware of the "graph
ref", a string like `id@variant` (but which might end up with other
spellings later).

We intend to remove the API key parser in Apollo Server 3 and stop
providing `graphId`/`graphVariant` to plugins and the gateway, but these
remain for now.

This PR:
- Allows you to specify the graph ref via `APOLLO_GRAPH_REF` or `apollo:
  {graphRef}`. It is an error to also specify ID or variant if you
  specify the ref.
- Makes `graphRef` available to plugins and the gateway alongside
  `graphId` and `graphRef`.
- If you specify an API key but it does not start with `service:` and
  you do not specify graph ref or graph ID, it throws an error. This
  fixes #4640. Note that while there are other legal Apollo key formats,
  Apollo Server only currently works with `service:*` keys.
- If you specify an API key but don't specify a graph ref or ID, prints a deprecation
  warning telling you to set a graph ref.
- Switches usage reporting and schema reporting to use new protocols
  that specify the graph ref instead of the variant, and to print Studio
  URLs that use the graph ref instead of the ID and variant separately.
  (The old protocols didn't specify the ID because it was implied by the
  API key.)
- The schema reporter previously used Apollo Codegen without any
  documentation of how it worked. Set up graphql-code-generator instead
  and add an npm script to regenerate the types.

Part of #5157.

 - apollo-cache-control@0.14.0-alpha.0
 - apollo-datasource-rest@0.14.0-alpha.0
 - apollo-reporting-protobuf@0.8.0-alpha.0
 - apollo-server-azure-functions@2.25.0-alpha.0
 - apollo-server-cloud-functions@2.25.0-alpha.0
 - apollo-server-cloudflare@2.25.0-alpha.0
 - apollo-server-core@2.25.0-alpha.0
 - apollo-server-express@2.25.0-alpha.0
 - apollo-server-fastify@2.25.0-alpha.0
 - apollo-server-hapi@2.25.0-alpha.0
 - apollo-server-integration-testsuite@2.25.0-alpha.0
 - apollo-server-koa@2.25.0-alpha.0
 - apollo-server-lambda@2.25.0-alpha.0
 - apollo-server-micro@2.25.0-alpha.0
 - apollo-server-plugin-base@0.13.0-alpha.0
 - apollo-server-plugin-operation-registry@0.11.0-alpha.0
 - apollo-server-plugin-response-cache@0.9.0-alpha.0
 - apollo-server-testing@2.25.0-alpha.0
 - apollo-server-types@0.9.0-alpha.0
 - apollo-server@2.25.0-alpha.0
 - apollo-tracing@0.15.0-alpha.0
 - graphql-extensions@0.15.0-alpha.0

It's a bit overkill. New plan is not to make "key but no ref" an error
in AS3 but just have it log a line noting that usage reporting is not
automatically installed.

 - apollo-server-azure-functions@2.25.0-alpha.1
 - apollo-server-cloud-functions@2.25.0-alpha.1
 - apollo-server-cloudflare@2.25.0-alpha.1
 - apollo-server-core@2.25.0-alpha.1
 - apollo-server-express@2.25.0-alpha.1
 - apollo-server-fastify@2.25.0-alpha.1
 - apollo-server-hapi@2.25.0-alpha.1
 - apollo-server-integration-testsuite@2.25.0-alpha.1
 - apollo-server-koa@2.25.0-alpha.1
 - apollo-server-lambda@2.25.0-alpha.1
 - apollo-server-micro@2.25.0-alpha.1
 - apollo-server-testing@2.25.0-alpha.1
 - apollo-server@2.25.0-alpha.1

 - apollo-cache-control@0.14.0
 - apollo-datasource-rest@0.14.0
 - apollo-reporting-protobuf@0.8.0
 - apollo-server-azure-functions@2.25.0
 - apollo-server-cloud-functions@2.25.0
 - apollo-server-cloudflare@2.25.0
 - apollo-server-core@2.25.0
 - apollo-server-express@2.25.0
 - apollo-server-fastify@2.25.0
 - apollo-server-hapi@2.25.0
 - apollo-server-integration-testsuite@2.25.0
 - apollo-server-koa@2.25.0
 - apollo-server-lambda@2.25.0
 - apollo-server-micro@2.25.0
 - apollo-server-plugin-base@0.13.0
 - apollo-server-plugin-operation-registry@0.11.0
 - apollo-server-plugin-response-cache@0.9.0
 - apollo-server-testing@2.25.0
 - apollo-server-types@0.9.0
 - apollo-server@2.25.0
 - apollo-tracing@0.15.0
 - graphql-extensions@0.15.0