Add optional argument to `ApolloServer.executeOperation` allowing the caller to manually specify an argument to the `config` function analogous to that provided by integration packages.

It is the caller's responsibility to figure out what should go in that argument and keep it up to date as they upgrade Apollo Server.

Fixes #2886.

Co-authored-by: David Glasser <glasser@davidglasser.net>

It's a peer dep so it doesn't get installed by default (on older npm at least).

The change to the code was necessary due to
DefinitelyTyped/DefinitelyTyped#49130 which ironically
was apparently submitted to support Apollo!

Also remove unnecessary @types/cors dependency from apollo-server-koa.

Fixes #5055.

See #5060.

This is a regression in #4981. If the server start process is begun implicitly
by the execution of an operation (ensureStarted inside graphQLServerOptions) and
startup throws, the log-and-redact logic wasn't being invoked.

Note that this case doesn't usually happen in practice, because:
- If you're using `apollo-server`, startup is begun in `listen()` before you can
  serve requests
- If you're using a serverless framework integration, startup is begun in the
  constructor
- If you're using a non-serverless framework integration, the function you call
  to connect it to your framework begins startup with `ensureStarting()`

So mostly this just affects the case that you're running `executeOperation`
without calling `start()` or `listen()`, or maybe you have your own custom
framework integration that doesn't call `ensureStarting()`. But it's still worth
missing.

Add some tests of this behavior and fix some TypeScript issues in the test file.

Co-authored-by: Renovate Bot <bot@renovateapp.com>

Co-authored-by: Renovate Bot <bot@renovateapp.com>

Resolved CHANGELOG.md conflicts

- Remove a file that's not in the repo anymore
- Switch docs to a more current list of users

Co-authored-by: Jesse Rosenberger <git@jro.cc>

Co-authored-by: Renovate Bot <bot@renovateapp.com>

Co-authored-by: Renovate Bot <bot@renovateapp.com>

Co-authored-by: Renovate Bot <bot@renovateapp.com>

- Allow Redis client to be injected by using the `BaseRedisCache` class which contains the existing implementation logic without the client initialisation.
- Removes duplication between `RedisCache` and `RedisClusterCache`
- Fixes a bug where the result of delete is returned as a number, rather than a boolean. (Our TypeScript types have always declared that this function returns a boolean as `KeyValueCache.delete` should, but the actual implementation returned a number. This was not noticed because of the use of an `any` type.)

In my opinion, `BaseRedisCache` should really be `RedisCache` and the existing `RedisCache` + `RedisCacheCluster` should either be renamed to identify that they are using the ioredis client, or removed and left for the consumer of the library to implement/ inject the client using this method. But this would obviously be a breaking change so maybe one to think about for the future?

I've created an interface for the `RedisClient` rather than rely on the ioredis type as i do not believe apollo should be tied to the ioredis interface.

Fixes #4871. Fixes #4870. Fixes #5006.

chore(deps): update dependency gatsby-theme-apollo-docs to v4.7.2

Add docs and changelog. As part of doing this, realize that the implementation
in #5034 makes it annoying to inject a cluster client, so switch the new API to
decide about get vs mget based on which kind of client is passed to the base
class.

This typing was added in #3431; it looks like we put the `| null` in the wrong
place. Fortunately, a function that's OK with accepting a null argument and will
never return null can still typecheck with the new type.

Fixes #5009.

…5091)

This particular error can be trivially triggered by clients, so it doesn't make
sense to use `INTERNAL_SERVER_ERROR` for it. It seems like a good fit for
`BAD_USER_INPUT`, which previously was only used if you explicitly throw a
`UserInputError` in your app.

Fixes #3498.

 - apollo-datasource-rest@0.12.0-alpha.0
 - apollo-server-azure-functions@2.23.0-alpha.0
 - apollo-server-cache-redis@1.4.0-alpha.0
 - apollo-server-cloud-functions@2.23.0-alpha.0
 - apollo-server-cloudflare@2.23.0-alpha.0
 - apollo-server-core@2.23.0-alpha.0
 - apollo-server-errors@2.5.0-alpha.0
 - apollo-server-express@2.23.0-alpha.0
 - apollo-server-fastify@2.23.0-alpha.0
 - apollo-server-hapi@2.23.0-alpha.0
 - apollo-server-integration-testsuite@2.23.0-alpha.0
 - apollo-server-koa@2.23.0-alpha.0
 - apollo-server-lambda@2.23.0-alpha.0
 - apollo-server-micro@2.23.0-alpha.0
 - apollo-server-plugin-operation-registry@0.9.0-alpha.0
 - apollo-server-testing@2.23.0-alpha.0
 - apollo-server@2.23.0-alpha.0

If you totally swap out ioredis for a different implementation then maybe you can
use mget with cluster (or maybe ioredis will support that some day), so using a
more precise term makes sense.

This changes us to run stuff in Node 12 which is required for the latest verdaccio.

)

Fixes #5084.

The sooner we get out of the business of understanding Lambda event formats, the
better. But this fix should be good for now.

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

Even though this is going away in AS3, it's gotten really annoying. We can't
just assume that adding one to a port gives a listenable port. Fortunately we
can get the OS to choose a port for us. It was easier to make this fix by
rewriting the test to be async.

Fixes #5101

 - apollo-datasource-rest@0.12.0
 - apollo-server-azure-functions@2.23.0
 - apollo-server-cache-redis@1.4.0
 - apollo-server-cloud-functions@2.23.0
 - apollo-server-cloudflare@2.23.0
 - apollo-server-core@2.23.0
 - apollo-server-errors@2.5.0
 - apollo-server-express@2.23.0
 - apollo-server-fastify@2.23.0
 - apollo-server-hapi@2.23.0
 - apollo-server-integration-testsuite@2.23.0
 - apollo-server-koa@2.23.0
 - apollo-server-lambda@2.23.0
 - apollo-server-micro@2.23.0
 - apollo-server-plugin-operation-registry@0.9.0
 - apollo-server-testing@2.23.0
 - apollo-server@2.23.0