fix(deps): enforce single [email protected] across monorepo; standardize graphql-upload@^13; move libs to peerDependencies

[pyramation]

fix(deps): enforce single [email protected] across monorepo; standardize graphql-upload@^13; move libs to peerDependencies

Summary
Resolves the duplicate GraphQL modules issue by:

• Centralizing graphql version control in root package.json using resolutions (including a wildcard) to enforce [email protected] across all workspaces
• Standardizing graphql-upload to ^13.0.0 and @types/graphql-upload to ^15.x to ensure compatibility with GraphQL 15 and PostGraphile v4
• Moving graphql to peerDependencies in library packages (graphile-query, gql-ast, @launchql/query, graphile-test) to avoid nested copies
• Ensuring app packages (@launchql/server, @launchql/explorer) depend on graphql 15.5.2 to satisfy peers
• Removing per-package resolutions blocks to avoid conflicts and duplication

Verification

• Fresh install/build:
  • yarn cache clean --all && rm -rf node_modules && yarn install && yarn build
• Single version check:
  • yarn why graphql => Found [email protected] (single)
  • yarn list --pattern graphql => only [email protected] plus related libs (graphql-tag, graphql-upload, @types/graphql-upload)
• CI:
  • GitHub Actions container-job: success

Notes

• The original error stack referenced a globally installed @launchql/cli; the library changes here (peerDependencies for graphql) reduce the chance of duplicate graphql when consumers install these packages. If a globally installed CLI still sees duplication, ensure the global environment pins graphql to 15.5.x or matches the monorepo’s versions.

Repository/Run Context

• Link to Devin run: https://app.devin.ai/sessions/ea8a9c4d40724ad3b9367d55743ac7eb
• Requested by: Dan Lynch (@pyramation)

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring