Update graphql-tools monorepo

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@graphql-tools/mock (source)	9.1.3 -> 9.1.4
@graphql-tools/schema (source)	10.0.29 -> 10.0.30
@graphql-tools/utils (source)	10.10.3 -> 10.11.0

---

Release Notes

ardatan/graphql-tools (@​graphql-tools/mock)

v9.1.4

Compare Source

ardatan/graphql-tools (@​graphql-tools/schema)

v10.0.30

Compare Source

Patch Changes

• Updated dependencies
  [2118a80]:
  • @​graphql-tools/utils@​10.11.0
  • @​graphql-tools/merge@​9.1.6

ardatan/graphql-tools (@​graphql-tools/utils)

v10.11.0

Compare Source

Minor Changes

• #​7588
  2118a80
  Thanks @​EmrysMyrddin! - Add optional schema coordinate in error
  extensions. This extension allows to precisely identify the source of the error by automated tools
  like tracing or monitoring.

  This new feature is opt-in, you have to enable it using schemaCoordinateInErrors executor
  option.

  Caution: This feature, when enabled, will expose information about your schema. If you need to
  keep your schema private and secret, you should strip this attribute at serialization time before
  sending errors to the client.

  import { parse } from 'graphql'
  import { normalizedExecutor } from '@​graphql-tools/executor'
  import { getSchemaCoordinate } from '@​graphql-tools/utils'
  import schema from './schema'
  
  const result = await normalizedExecutor({
    schema,
    document: parse(`...`),
    schemaCoordinateInErrors: true // enable adding schema coordinate to graphql errors
  })
  
  if (result.errors) {
    for (const error of result.errors) {
      console.log('Error in resolver ', error.coordinate, ':', error.message)
      // or with `getSchemaCoordinate` util, to workaround types if needed
      console.log('Error in resolver', getSchemaCoordinate(error), ':', error.message)
    }
  }

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.