Simplify hooks logic

[wjhsf]

(This is a replay of #954 onto develop)

Over time, the implementations of query and mutation hooks have gotten a bit convoluted, and support has been added for features that we no longer deem necessary. This PR aims to simplify the signatures of the hooks and clean up the internal logic used.

As a result, query hooks now follow a pattern similar to:

const {
  data // Basket only, returning Response is no longer supported
} = useBasket(
  apiOptions // passed through to commerce-sdk-isomorphic
  queryOptions // passed through to @tanstack/react-query
)

Mutation hooks have also been simplified:

const { mutate } = useShopperBasketsMutation('createBasket') // Only takes the mutation name, now
mutate(apiOptions) // passed through to commerce-sdk-isomorphic

Under the hood, I've moved as much logic as I could from the endpoint hooks into the useQuery and useMutation helpers, to reduce repetition.

I've also refactored the query update logic. That must be implemented manually for each endpoint, so I've moved it out of the mutation.ts file, which is generated, and into a new config.ts file (per API, i.e. peer of mutation.ts). I've moved a lot of things around between the various locations (updateCache, useMutation, and the per-API methods), to hopefully simplify the interface as much as possible, and I've DRYed up some repeated logic.

In addition to cleaning up / fixing types, I made two major changes to query keys / cache updates: First, query keys previously only used parameters set on the options, but parameters can also be set on the config. So I've updated the logic to merge config/options before generating query keys / cache lookups. Secondly, we previously had cache lookup logic that accepted a query key, and created a lookup function from that. I've refactored the code so that we provide the lookup functions directly, which we can build from composable helpers. This provides us much more flexibility.

This PR will have a lot of file changes, so to keep review a bit more focused, I opened a separate PR with a snapshot, #981.

Description

Types of Changes

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Documentation update
• Breaking change (could cause existing functionality to not work as expected)
• Other changes (non-breaking changes that does not fit any of the above)

Breaking changes include:

• Removing a public function or component or prop
• Adding a required argument to a function
• Changing the data type of a function parameter or return value
• Adding a new peer dependency to package.json

Changes

• (change1)

How to Test-Drive This PR

• (step1)

Checklists

General

• Changes are covered by test cases
• CHANGELOG.md updated with a short description of changes (not required for documentation updates)

Accessibility Compliance

You must check off all items in one of the follow two lists:

• There are no changes to UI

or...

• Changes were tested with a Screen Reader (iOS VoiceOver or Android Talkback) and had no issues
• Changes comply with WCAG 2.0 guidelines levels A and AA
• Changes to common UI patterns and interactions comply with WAI-ARIA best practices

Localization

• Changes include a UI text update in the Retail React App (which requires translation)

[kevinxh]

The js comments like these are usually not updated often and certainly not in the process when we release API changes. I wonder if there is a better place for such notes. Just a nit worry that we might forget to remove it in the future.

[kevinxh]

The PR looks good to me, is it the intention to move the changes in pwa-kit-dev to another PR?