Make graphql-tools dependencies tree-shakable

[n1ru4l]

1. For Bundle Size
   1. Add Bundle Size checks (with images that would be nice)
   2. My long-term vision is to completely drop the @graphql-tools/utils and @graphql-tools/schema dependency from graphql-yoga as it makes up quite a big chunk of the whole bundle. (https://bundlephobia.com/package/@graphql-yoga/common@2.8.3).
   3. In the best-case scenario, the @graphql-tools/schema functionality for constructing a schema is part of graphql-js.
2. Remove the default schema because it needs makeExecutableSchema even if user passes their own schema
   • What about @graphql-yoga/common/schema? ✅
3. Export makeExecutableSchema from yoga in a tree shakable way and remove makeExecutableSchema from createServer so by default createServer would take less bundle size and makeExecutableSchema would be tree shaken/gone.
   • schema parameter will accept GraphQLSchema only and users will create the schema by themselves with the exported makeExecutableSchema or some other schema factory lib.
4. Stop supporting older graphql-js versions
   • If we continue to support older versions of GraphQL-js, we will need to use helper functions from @graphql-tools/utils
   • https://github.com/dotansimha/graphql-yoga/pull/1270/files#diff-0daee1344bf306ad107b97cd8ecef14dad3711468261445bc6db1a1d430bfc9eR2
   • Drop GraphQL.js 15 support #1304

[n1ru4l]

We decided upon, that we re-export the functionality under @graphql-yoga/common/schema

[n1ru4l]

Unfortunately, because of ESM and TypeScript limitations, we cannot simply provide deep imports.

Instead, we can mark all our files as side-effect free, which allows tree-shaking.

• https://webpack.js.org/guides/tree-shaking/#mark-the-file-as-side-effect-free

[ardatan]

@n1ru4l I think we can close this, no?

[n1ru4l]

yas