Expose context function args in executeOperation

[bitglue]

Fixes #2886

Integrations pass implementation-specific arguments to the context
function, but executeOperation passes no arguments. This allows the
caller of executeOperation to specify those arguments, either to emulate
the behavior of an integration or to achieve some other user-specific
behavior. This seems appropriate, as the context function is the
designated entry point for such user-specific behavior.

[apollo-cla]

@bitglue: Thank you for submitting a pull request! Before we can merge it, you'll need to sign the Apollo Contributor License Agreement here: https://contribute.apollographql.com/

[bitglue]

I'm pretty new to typescript, so sorry if this is a stupid question, but is there something I need to do to update the compiled javascript? I tried running npm compile, but that didn't change anything in dist/.

[glasser]

I asked some questions about this approach on #2886.

npm run compile should rebuild all the packages/*/dist. If it doesn't work, try npm run clean before it?

[glasser]

Er actually, run npm run clean and then npm install as the clean wipes out all the node_modules.

[glasser]

OK, this overall approach makes sense to me, though I might need to think more about the details. Adding this to my list for my next "focus on PRs which require at least a bit of thought" day.

[bitglue]

We've solved this problem by using graphql-js directly rather than apollo. This PR doesn't seem to be going anywhere so closing to get it off my list.

[glasser]

@bitglue as you can see on the linked issue #2886, we fixed this in April with #4166, released in Apollo Server 2.23.0.

At some point in the process, I must have forgotten that there were two separate contributed PRs for the same fix and I never followed up here, sorry!