Fix schema type printer for default values

[emmatown]

This is sorta wrong because we actually need to model the input and coerced inputs as different things but the main place where people are practically using these types today is the lists API so I think catering for the uncoerced input is better than catering for the coerced input types.

This is for #5767 and #5777

[changeset-bot]

🦋 Changeset detected

Latest commit: bdd7f92

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

This PR includes changesets to release 2 packages

Name	Type
@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/GK61i6K1VYQsapKkPTrHXfu23rTc
✅ Preview: https://keystone-next-git-fix-schema-type-printer-for-default-v-38630b.vercel.app

[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 bdd7f92:

Sandbox	Source
@keystone-next/example-sandbox	Configuration

[timleslie]

👍