Only coerce items API input when using resolveFields: false

[timleslie]

The argument coercion applied in the items API should only be done in the code path where we're calling the mutations directly. In the case where we go through the GraphQL API itself we don't want to do this. For most field types it doesn't make a different but for Upload types it will convert an object of the form

    {
      upload: Upload {
        resolve: [Function],
        reject: [Function],
        promise: Promise { [Object] },
        file: {
          createReadStream: [Function: createReadStream],
          filename: 'keystone.jpeg',
          mimetype: 'image/jpeg',
          encoding: 'utf-8'
        }
      }
    }

into

    {
      upload: Promise {
        {
          createReadStream: [Function: createReadStream],
          filename: 'keystone.jpeg',
          mimetype: 'image/jpeg',
          encoding: 'utf-8'
        }
      }
    }

which doesn't work as an input with the graphql() function which we use to execute server side GraphQL

[changeset-bot]

🦋 Changeset detected

Latest commit: a550f75

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 5 packages

Name	Type
@keystone-next/server-side-graphql-client-legacy	Patch
@keystone-next/keystone	Patch
@keystone-next/test-utils-legacy	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/keystonejs/keystone-next-docs/BaKrMdjnWbej2toqcRZdHpwHkk3d
✅ Preview: https://keystone-next-docs-git-item-api-coerce-data-keystonejs.vercel.app

[timleslie]

The changes in this PR allow this test to be re-written with the items API, where previously it would fail.

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit a550f75:

Sandbox	Source
@keystone-next/example-sandbox	Configuration

[emmatown]

I believe this is incorrect, I'm going to look into it more.

[emmatown]

I was incorrect, I interpreted this as "stop coercing the inputs completely" when really this is "let the graphql function coerce the inputs"