Bump apollo-cache-inmemory from 1.5.1 to 1.6.0 in /webapp

Sourced from apollo-cache-inmemory's changelog.

Apollo Cache In-Memory 1.6.0

• Support new InMemoryCache({ freezeResults: true }) to help enforce immutability.
  @​benjamn in #4514

• Allow IntrospectionFragmentMatcher to match fragments against the root Query, as HeuristicFragmentMatcher does.
  @​rynobax in #4620

• Rerential identity (===) of arrays in cache results will now be preserved for unchanged data.
  @​benjamn in commit f3091d6a

• Avoid adding __typename field to @client selection sets that have been @exported as input variables.
  @​benjamn in #4784

GraphQL Anywhere 4.2.2

• The graphql function can now be configured to ignore @include and @skip directives (useful when walking a fragment to generate prop types or filter result data).
  @​GreenGremlin in #4373

Apollo Client 2.5.1

apollo-client 2.5.1

• Fixes A tuple type element list cannot be empty issue.
  @​benjamn in #4502

graphql-anywhere 4.2.1

• Adds back the missing graphql-anywhere/lib/async entry point.
  @​benjamn in #4503

Apollo Client (2.5.0)

Apollo Client (2.5.0)

• Introduces new local state management features (client-side schema and local resolver / @client support) and many overall code improvements, to help reduce the Apollo Client bundle size.
  #4361
• Revamped CJS and ESM bundling approach with Rollup.
  @​rosskevin in #4261
• Fixes an issue where the QueryManager was accidentally returning cached data for network-only queries.
  @​danilobuerger in #4352
• Fixed an issue in the repo .gitattributes that was causing binary files to have their line endings adjusted, and cleaned up corrupted documentation

... (truncated)

• 6838c5b chore: Publish
• 7eaf413 Merge pull request #4586 from apollographql/release-2.6.0
• 136ce43 Revert "Temporarily publish to npm using the beta tag."
• 6c348e9 Update CHANGELOG.md with final 2.6.0 changes and package versions.
• b64b4e9 chore: Publish
• bcd3aff Preserve cache-and-network fetchPolicy when refetching. (#4840)
• b78bb88 Add a regression test for issue #4841.
• 1268057 Merge branch 'master' into release-2.6.0
• 00261df Run all QueryManager tests (#4842)
• e5c9e9b chore(deps): update dependency gatsby to v2.5.5 (#4836)
• Additional commits viewable in compare view

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot ignore this [patch|minor|major] version will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)

Finally, you can contact us by mentioning @dependabot.