feat: update @graphql-tools/utils version to 11.0.0

[thisisnithin]

Summary by CodeRabbit

• Chores
  • Updated GraphQL tools utilities dependency to version 11.0.0 across multiple packages.
• Style
  • Minor GraphQL schema formatting and directive repositioning in the demo subgraph (no functional changes).

Checklist

• I have discussed my proposed changes in an issue and have received approval to proceed.
• I have followed the coding standards of the project.
• Tests or benchmarks have been added or updated.
• Documentation has been updated on https://github.com/wundergraph/cosmo-docs.
• I have read the Contributors Guide.

[coderabbitai]

Walkthrough

Dependency version for "@graphql-tools/utils" is updated to "11.0.0" across four package.json files (cli, composition, controlplane, and shared), with version constraints preserved where applicable. No code logic or control flow changes.

Changes

Cohort / File(s)	Summary
Dependency Updates cli/package.json, composition/package.json, controlplane/package.json, shared/package.json	Updated "@graphql-tools/utils" dependency to version 11.0.0 across all four package.json files, with version specifiers (exact and caret ranges) preserved.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• feat: make dependency versions be fixed #2357: Also modifies "@graphql-tools/utils" dependency declarations in package.json files with version updates.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately and specifically describes the main change: updating @graphql-tools/utils to version 11.0.0 across multiple package.json files.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 43.25%. Comparing base (89cb868) to head (b4ec578).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2495      +/-   ##
==========================================
+ Coverage   43.13%   43.25%   +0.11%     
==========================================
  Files        1015     1015              
  Lines      142011   142011              
  Branches     8888     8900      +12     
==========================================
+ Hits        61256    61424     +168     
+ Misses      79145    78978     -167     
+ Partials     1610     1609       -1     

see 16 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[github-actions]

Router image scan passed

✅ No security vulnerabilities found in image:

ghcr.io/wundergraph/cosmo/router:sha-54a240ca503622d4ac71a02cd12b2a057e293959

[github-actions]

Router-nonroot image scan passed

✅ No security vulnerabilities found in image:

ghcr.io/wundergraph/cosmo/router:sha-c539aff6a867d36a25cd1ffe79052c213b5f3dc7-nonroot

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@controlplane/package.json`:
- Line 52: After upgrading `@graphql-tools/utils` to v11 where
printSchemaWithDirectives emits operation types as extensions, verify and adjust
schema generation in controlplane/src/core/composition/composer.ts: re-run or
update the logic that builds federatedGraphSchema and federatedClientSchema to
handle operation type extensions (instead of expecting omitted/rewritten
operation types), ensure printSchemaWithDirectives output is normalized before
comparisons (e.g., canonicalize or strip/merge operation type extension
definitions) and update snapshot tests or schema comparisons to match the new
output format so tests pass and the composed schemas remain semantically
equivalent.

[StarpTech]

LGTM