consolidate Request and ExecutionParams types

[yaacovCR]

• also affixes rootValue to Request
• when delegating with delegateToSchema, rootValue can be set multiple ways:
  • when using a custom executor, the custom executor can utilize a
    rootValue in whichever custom way it specifies.
  • when using the default executor (execute/subscribe from graphql-js):
    -- rootValue can be passed to delegateToSchema via a named option
    -- rootValue can be included within a subschemaConfig
    -- otherwise, rootValue is inferred from the originating schema

• when using wrapSchema/stitchSchemas, a subschemaConfig can specify the
  createProxyingResolver function which can pass whatever rootValue it
  wants to delegateToSchema as above.

[changeset-bot]

🦋 Changeset detected

Latest commit: 3931762

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 25 packages

Name	Type
@graphql-tools/batch-delegate	Major
@graphql-tools/batch-execute	Major
@graphql-tools/delegate	Major
@graphql-tools/links	Major
@graphql-tools/url-loader	Major
@graphql-tools/stitch	Major
@graphql-tools/utils	Major
@graphql-tools/wrap	Major
@graphql-tools/stitching-directives	Patch
@graphql-tools/prisma-loader	Patch
@graphql-tools/graphql-tag-pluck	Patch
@graphql-tools/load	Patch
@graphql-tools/merge	Patch
@graphql-tools/mock	Patch
@graphql-tools/node-require	Patch
@graphql-tools/relay-operation-optimizer	Patch
@graphql-tools/resolvers-composition	Patch
@graphql-tools/schema	Patch
@graphql-tools/apollo-engine-loader	Patch
@graphql-tools/code-file-loader	Patch
@graphql-tools/git-loader	Patch
@graphql-tools/github-loader	Patch
@graphql-tools/graphql-file-loader	Patch
@graphql-tools/json-file-loader	Patch
@graphql-tools/module-loader	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[theguild-bot]

The latest changes of this PR are available as alpha in npm (based on the declared changesets):

@graphql-tools/batch-delegate@8.0.0-alpha-d79e1771.0
@graphql-tools/batch-execute@8.0.0-alpha-d79e1771.0
@graphql-tools/delegate@8.0.0-alpha-d79e1771.0
@graphql-tools/graphql-tag-pluck@6.5.2-alpha-d79e1771.0
graphql-tools@7.0.6-alpha-d79e1771.0
@graphql-tools/links@8.0.0-alpha-d79e1771.0
@graphql-tools/load@6.2.9-alpha-d79e1771.0
@graphql-tools/apollo-engine-loader@6.2.6-alpha-d79e1771.0
@graphql-tools/code-file-loader@6.3.2-alpha-d79e1771.0
@graphql-tools/git-loader@6.2.7-alpha-d79e1771.0
@graphql-tools/github-loader@6.2.6-alpha-d79e1771.0
@graphql-tools/graphql-file-loader@6.2.8-alpha-d79e1771.0
@graphql-tools/json-file-loader@6.2.7-alpha-d79e1771.0
@graphql-tools/module-loader@6.2.8-alpha-d79e1771.0
@graphql-tools/prisma-loader@6.3.1-alpha-d79e1771.0
@graphql-tools/url-loader@7.0.0-alpha-d79e1771.0
@graphql-tools/merge@6.2.15-alpha-d79e1771.0
@graphql-tools/mock@8.1.4-alpha-d79e1771.0
@graphql-tools/node-require@6.2.5-alpha-d79e1771.0
@graphql-tools/relay-operation-optimizer@6.3.1-alpha-d79e1771.0
@graphql-tools/resolvers-composition@6.2.9-alpha-d79e1771.0
@graphql-tools/schema@7.1.6-alpha-d79e1771.0
@graphql-tools/stitch@8.0.0-alpha-d79e1771.0
@graphql-tools/stitching-directives@1.3.4-alpha-d79e1771.0
@graphql-tools/utils@8.0.0-alpha-d79e1771.0
@graphql-tools/wrap@8.0.0-alpha-d79e1771.0

[yaacovCR]

Reference:

https://github.com/graphql/graphql-spec/blob/086bb1f1a7f273b6d0787de525f1c23742374ae0/rfcs/glossary/Appendix%20C%20--%20Glossary.md#graphql-request

rootValue is the initialValue by the spec

[yaacovCR]

I think our Request type can have context/info in it, optional properties that make sense only when the request originates from within execution of a parent GraphQL Request.

It probably makes sense to eventually put these within the extensions map, but I think this is fine for now.

Thoughts?