chore: fix using flawed useQuery hook from @apollo/client

[ElviraBurchik]

Description

#545 broke queries in the fixture app. The latest version of @apollo/client has a bug where the useQuery loading state stays true after fetch finishes - #6334, so when #545 replaced deprecated @apollo/react-hooks with @apollo/client, and the issue became prominent.

Suggested solution to the problem is to downgrade @apollo/client for now, this PR fixes the problem.

Reviewers’ hat-rack 🎩

Checklist

• I have added a decision record entry, PR includes changes to monorepo setup that may require explanation
• I have added a changelog entry following the Keep a Changelog guidelines.

[caution-tape-bot]

👋 It looks like you're updating JavaScript packages that are known
to cause problems when duplicated.

You can deduplicate them with the yarn-deduplicate utility:

npx yarn-deduplicate --packages graphql react react-dom webpack
npx yarn-deduplicate --scopes @shopify @apollo

If running these commands doesn't produce a change in your yarn.lock file,
you didn't have duplications in these packages and can carry on.

A duplicate React version may cause an invalid hook call warning.

React context providers usually use module-scoped globals as their
default context values. Multiple versions of such packages will yield
multiple global instances, resulting in oblique runtime errors.