fix(deps): update graphql-tools monorepo

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@graphql-tools/merge (source)	9.1.9 → 9.1.10
@graphql-tools/schema (source)	10.0.33 → 10.0.34
@graphql-tools/utils (source)	11.1.0 → 11.1.1

---

Release Notes

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

v9.1.10

Compare Source

Patch Changes

• Updated dependencies
  [981d461]:
  • @​graphql-tools/utils@​11.1.1

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

v10.0.34

Compare Source

Patch Changes

• Updated dependencies
  [981d461]:
  • @​graphql-tools/utils@​11.1.1
  • @​graphql-tools/merge@​9.1.10

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

v11.1.1

Compare Source

Patch Changes

• #​8256
  981d461
  Thanks @​twavv! - Fix mergeDeep returning undefined instead of {}
  when merging two or more empty objects.

  Previously the output accumulator was only initialized inside the per-key loop, so merging sources
  with no own keys (e.g. mergeDeep([{}, {}])) left it undefined. This silently dropped
  empty-object values during nested merges ({ data: {} } became { data: undefined }), which
  could surface as "Cannot return null for non-nullable field" errors when stitching schemas. The
  accumulator is now initialized as soon as an object source is encountered.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ 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.