extendSchema: preserve "description" and "extensions"

[igrlk]

👋

Closes #3629

Current behavior:

When calling extendSchema(schema, schemaModification), extended schema description is calculated as schemaDef?.description?.value, where

• schemaDef is a nullable schema definition, that will not be null only if schemaModification declares the type schema (it happens only when we call buildSchema or call extendSchema(schema, 'extend type __Schema { ... }'))
• schemaDef?.description is not undefined only when extendSchema is called from buildSchema, otherwise it's undefined because we don't allow a construction like:

"my awesome description" // error - graphql-js doesn't allow you to set the description when you extend schema
extend type __Schema { ... }

As a result, every extendSchema call besides the one in buildSchema will cause description to become undefined

Proposed solution:

Always fallback to the original schema description:
description: schemaDef?.description?.value ?? schemaConfig.description

It will allow us to make sure that we take a description from schemaDef when schema is being built and take original schema description in any other cases

[netlify]

✅ Deploy Preview for compassionate-pike-271cb3 ready!

Name	Link
🔨 Latest commit	5693423
🔍 Latest deploy log	https://app.netlify.com/sites/compassionate-pike-271cb3/deploys/637b709375931b0008ef6d75
😎 Deploy Preview	https://deploy-preview-3776--compassionate-pike-271cb3.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[github-actions]

Hi @igrlk, I'm @github-actions bot happy to help you with this PR 👋

Supported commands

Please post this commands in separate comments and only one per comment:

• @github-actions run-benchmark - Run benchmark comparing base and merge commits for this PR
• @github-actions publish-pr-on-npm - Build package from this PR and publish it on NPM

[IvanGoncharov]

Hi @igrlk
Thank you for this PR, I also noticed that we have the exact same problem with extensions so I fixed it in the same PR.

[igrlk]

Thank you, @IvanGoncharov!