[packages] match few dependencies to the workspace versions

[Simek]

Why

Refs #14561

How

This PR bumps the few dependencies in the Expo packages to match theirs versions to the latest versions used in the workspace.

Test Plan

yarn and yarn test (if available) commands in the modified packages directories have ended with success.

Checklist

• Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md).
• This diff will work correctly for expo build (eg: updated @expo/xdl).
• This diff will work correctly for expo prebuild & EAS Build (eg: updated a module plugin).

[expo-bot]

Hi there! 👋 I'm a bot whose goal is to ensure your contributions meet our guidelines.

I've found some issues in your pull request that should be addressed (click on them for more details) 👇

⚠️ Suggestion: Missing changelog entries

Your changes should be noted in the changelog. Read Updating Changelogs guide and consider (it's optional) adding an appropriate entry to the following changelogs:

• packages/expo-camera/CHANGELOG.md
• packages/expo-dev-menu/CHANGELOG.md
• packages/expo-modules-autolinking/CHANGELOG.md

---

Generated by ExpoBot 🤖 against 386ce87

[ide]

LGTM but first would like to see an explanation or test plan validating the graphql package ugprade.

[ide]

Is this breaking change safe? Cf. https://github.com/graphql/graphql-js/releases/tag/v15.0.0

[Simek]

@ide I have updated earlier GraphQL in Home app, and there was a bit of migration/refactor needed, but from my checks it looks like GraphQL in dev-menu is used very sparse, maybe there are several lines and few method/imports used (all from graphql-tag package). So it looks like the GraphQL is just a required dependency which is not used directly in the code.

[ide]

Being sparsely used doesn't mean it's safe to upgrade. I looked into graphql-tag's commit history to see when support for graphql@15 was confirmed/added. It turns out that happened here, which was included in [email protected]. yarn why says we use [email protected] everywhere so we have the updated version and bumping the graphql version is safe, but we need to understand why dependency upgrades are safe before doing them.

[Simek]

@ide Yup, I agree. Thank you for the check and dependencies relation analysis!